The logo text should be white in color in the readme while the dark mode is active for better visibility. White color contrasts the best with the background color, and it makes for a better UI.

Kindly share your views on this issue.

AB#656

If you are trying to resolve an environment-specific issue or have a one-off question about the edge case that does not require a feature then please consider asking a question in Devtron Discord channel.

Checklist:

• [ ] I've searched in the docs and FAQ for my answer
• [ ] I've included steps to reproduce the bug.

Describe the bug

A clear and concise description of what the bug is.

To Reproduce

[ordered list the process to finding and recreating the issue, example below]

1. User goes to Create an application (to save space or whatever)
2. User selects clone option
3. Configmap in environment override is not cloned

Expected behavior

A clear and concise description of what you expected to happen.

Current behavior

describe what you currently experienced from this process, and thereby explain the bug

Screenshots

If applicable, add screenshots to help explain your problem.

Logs

Paste any relevant application logs here.

Describe the bug

When trying to install devtron on Kubernetes 1.22 I get the following error:

$ helm repo add devtron https://helm.devtron.ai "devtron" has been added to your repositories $ helm install devtron devtron/devtron-operator --create-namespace --namespace devtroncd Error: INSTALLATION FAILED: failed to install CRD crds/crd-devtron-legacy.yaml: error parsing : json: offset 2: invalid character '{' looking for beginning of object key string

To Reproduce

1. Execute "helm repo add devtron https://helm.devtron.ai"
2. helm install devtron devtron/devtron-operator --create-namespace --namespace devtroncd
3. Install does not start

Expected behavior

Devtron should install.

Current behavior

Devtron does not install.

💭 Description

Where: https://github.com/devtron-labs/devtron/blob/main/README.md What: "Implements GitOps to manage the state of Kubernetes applications," ends in "," and should be a ".", according to other examples.

Screenshot:

P.S. Please apply "good first time issue" label.

👀 Have you spent some time to check if this issue has been raised before?

• [X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• [X] I have read the Code of Conduct

AB#1006

Summary

We would like to have docker buildx in the CI step, which would help us build multi-platform images with Devtron (which can run within amd, arm etc processors).

Motivation

Presently, Devtron runs CI pipelines with docker build command which we think is hardcoded as part of CI step. We would want to use docker buildx command which supports a lot of features on top of the good old docker build. buildx would help us in building multi-platform images which can run on all types of processors. https://docs.docker.com/buildx/working-with-buildx/#build-multi-platform-images

Proposal

We would like Devtron to provide buildx option in the CI pipelines. Few additional options can also be provided to the user to choose which platform images the user wants to build. Or, it can also be provided as part of Global Configurations, where the Admins can select the platform(s) (amd, arm etc) for which all the apps need to build their images.

📜 Description

Created a kind cluster on 1.22.7 k8s version. Installed devtron using helm chart. When tried to install GitOps (Argo CD) from the UI, it got stuck in installing state and I see argocd-application-controller and argocd-server pods are in CrashLoopBackOff state.

argocd-application-controller-0 pod logs argocd-server pod logs:

👟 Reproduction steps

Install a kind cluster with below kind configurations: `kind: Cluster apiVersion: kind.x-k8s.io/v1alpha4 networking: podSubnet: "10.214.0.0/16" serviceSubnet: "10.16.0.0/12" nodes:

• role: control-plane image: kindest/node:v1.22.7@sha256:1dfd72d193bf7da64765fd2f2898f78663b9ba366c2aa74be1fd7498a1873166 extraPortMappings:
  • containerPort: 30000 hostPort: 30000
• role: worker image: kindest/node:v1.22.7@sha256:1dfd72d193bf7da64765fd2f2898f78663b9ba366c2aa74be1fd7498a1873166
• role: worker image: kindest/node:v1.22.7@sha256:1dfd72d193bf7da64765fd2f2898f78663b9ba366c2aa74be1fd7498a1873166 `

and use devtron helm chart to install devtron

👍 Expected behavior

When installing Argo CD. Pods should spin up and installation should be successful.

👎 Actual Behavior

Argo pods go into CrashLoopBackOff state

💻 Device

Desktop/Laptop

💻 Operating system

MacOS

🌍 Browser

Chrome

🧱 Your Environment

I use kind for creating a k8s version 1.22.7 cluster

✅ Proposed Solution

No response

👀 Have you spent some time to check if this issue has been raised before?

• [X] I checked and didn't find any similar issue

🏢 Have you read the Code of Conduct?

• [X] I have read the Code of Conduct

AB#620

Summary

In pre and post-deployment steps, it is useful to have the commit hash/sha as an environment variables, which we could use for example in webhook calls.

Motivation

Let's say we need to integrate with a third-party tool that provides deployment analytics. In such a case, their webhooks require us to append the commit hash. While it is very easy to add a post-deployment step, currently not having the commit hash is being a blocker in integrating with such tooling.

Proposal

Having the git hash provided as an environment variable during the pre and post deployment steps.

AB#365

Checklist:

• [x] I've searched in the docs and FAQ for my answer
• [x] I've included steps to reproduce the bug.

Describe the bug

I deployed an app with AWS external-secret as secret all things running fine secrets are being used in the pod, even it shows degraded in-app status.

To Reproduce

[ordered list the process to finding and recreating the issue, example below]

1. Create a custom app with AWS external-secret as secret.
2. Deploy the app.
3. Check the status of the app

Expected behavior

The app status should show healthy when everything running well.

Current behavior

Even after all things running fine but status is degraded.

Screenshots

AB#311

Summary

Allow managers to give permission to any users even they are added by other managers. Manager won't give permission today if user has already access for environment which he has not part of.

Motivation

Restriction need to remove for managers.

Proposal

Re-visit the user access module.

AB#50

Obfuscate or skip logging sensitive info (passwords, keys etc) in the console until debug mode is enabled

Checklist:

• [x] I've searched in the docs and FAQ for my answer
• [x] I've included steps to reproduce the bug.

Describe the bug

Some micro-services log sensitive info in the console logs, which should not be done until debug mode is enabled. Check the following micro-services:

1. Git-sensor
2. Devtron Orchestrator
3. Ci-runner

Expected behavior

Logs should not contain any sensitive info like passwords, keys, tokens etc.

Current behavior

Some micro-services log sensitive info on console.

Summary

We want to run our automation suite using Devtron pipeline. For that we need pipeline to get triggered based on cron.

Proposal

1. Create schedules based on cron.
2. Add pipeline variables so that we can run job based on pipeline variable.

AB#284

📜 Description

helm generated manifest output is not coming for helm apps other than unlinked cli helm apps.

👟 Reproduction steps

1. Deploy an app using app store or link a cli helm app.
2. manifest output tab will be missing in deployment history.

👍 Expected behavior

helm generated manifest output tab should come for all helm apps just like unlinked CLI helm apps.

👎 Actual Behavior

helm generated manifest output tab is not coming for all helm apps other than unlinked CLI helm apps.

☸ Kubernetes version

EKS 1.2.3

Cloud provider

🌍 Browser

Chrome

🧱 Your Environment

No response

✅ Proposed Solution

No response

👀 Have you spent some time to check if this issue has been raised before?

• [X] I checked and didn't find any similar issue

🏢 Have you read the Code of Conduct?

• [X] I have read the Code of Conduct

Description

This PR fixes two issues:-

1. helm generated manifest output was not coming for helm apps other than unlinked cli helm apps.
2. Deployment history was coming for app store helm apps. It was only coming after app is updated.

Fixes #2823

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

1. By checking that helm generated manifest output is coming for all helm apps or not.

Checklist:

• [ ] The title of the PR states what changed and the related issues number (used for the release note).
• [ ] Does this PR requires documentation updates?
• [ ] I've updated documentation as required by this PR.
• [x] I have performed a self-review of my own code.
• [x] I have commented my code, particularly in hard-to-understand areas.
• [x] I have tested it for all user roles.
• [ ] I have added all the required unit/api test cases.

Does this PR introduce a user-facing change?

Description

Migrated to common lib pubsub client code instead of local pubsub client

Fixes # (issue) https://github.com/devtron-labs/devtron/issues/2281

Type of change

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• [x] Tested the events coming from kubewatch in ci-build

Checklist:

• [x] The title of the PR states what changed and the related issues number (used for the release note).
• [ ] Does this PR require documentation updates?
• [ ] I've updated documentation as required by this PR.
• [ ] I have performed a self-review of my own code
• [ ] I have commented my code, particularly in hard-to-understand areas
• [ ] I have tested it for all user roles
• [ ] I have added all the required unit/api test cases

📜 Description

china gfw network blocking,i try to install CI/CD, response "dial tcp 0.0.0.0:443: connect: connection refused"

👟 Reproduction steps

1.install or Retry install

👍 Expected behavior

install success

👎 Actual Behavior

Get "https://raw.githubusercontent.com/devtron-labs/devtron/v0.6.9/charts/devtron/devtron-bom.yaml": dial tcp 0.0.0.0:443: connect: connection refused

response : {"code":500,"status":"Internal Server Error","errors":[{"code":"000","internalMessage":"[{Get "https:/ /raw.githubusercontent.com/devtron-labs/devtron/v0.6.9/charts/devtron/devtron-bom.yaml": dial tcp 0.0.0.0:443: connect: co nnection refused}]","userMessage":"Get "https://raw.githubusercontent.com/devtron-labs/devtron/v0.6.9/charts/devtron/devtr on-bom.yaml": dial tcp 0.0.0.0:443: connect: connection refused"}]}

☸ Kubernetes version

k3d

Cloud provider

self-hosted

🌍 Browser

Chrome

🧱 Your Environment

No response

✅ Proposed Solution

This is a request from the golang http package,I want to use golang http proxy download devtron-bom.yaml Or use other methods to successfully download . What should I do

👀 Have you spent some time to check if this issue has been raised before?

• [X] I checked and didn't find any similar issue

🏢 Have you read the Code of Conduct?

• [X] I have read the Code of Conduct

🔖 Feature description

A feature like Resource viewer for a cluster is very useful for users who want to view all the k8s resources for a k8s cluster and want to take any action (create resource, delete resource, edit resource) on that cluster. Currently users do these things from cli, so exposing a fine UI on dashboard for these will be better for users.

🎤 Pitch

A button on left panel can be exposed and on clicking on that user should ask to select cluster. after selecting the cluster, Resource viewer should get open.

✌️ Solution

Resource viewer should give a complete picture of all the resources which are part of that cluster and user can take actions against them.

🔄️ Alternative

NA

👀 Have you spent some time to check if this issue has been raised before?

• [X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• [X] I have read the Code of Conduct