lightbend / console-charts Goto Github PK

Got this email from Circle today. We need to upgrade the ubuntu image version used in our circle config:

Hello,

We are deprecating Ubuntu 16.04-based machine images on CircleCI in preparation for an EOL on Tuesday, May 31, 2022 to ensure your builds remain secure. For a detailed overview of how this will affect your workflow, read the blog article here.

We will also be conducting temporary brownouts on Tuesday, March 29, 2022, and again on Tuesday, April 26, 2022 during which these images will be unavailable.

We are contacting you because one or more of your projects has a job that uses an Ubuntu 16.04-based image.

The project(s) using an image based on Ubuntu 16.04 are:

[console-charts]

If you have specified an Ubuntu 16.04-based image please see our migration guide to upgrade to a newer version of Ubuntu image in order to avoid any service disruption during the brownout & subsequent EOL.

We will also be releasing a CircleCI Ubuntu 22.04 image on April 22nd offering the flexibility to upgrade to the latest LTS version of Ubuntu image before we remove older versions permanently. A beta version of the image will be available March 21st.

Our team is committed to getting you the most performant builds while maintaining security.

While we have been trying to update old references to https://lightbend.github.io/helm-charts, some still remain (including some on third-party web sites that are out of our control). If we can avoid breaking this URL, it would be better.

Renaming this repository from helm-charts to console-charts seems to have broken the old URL, as GitHub pages isn't redirecting automatically from https://lightbend.github.io/helm-charts/index.yaml to https://lightbend.github.io/console-charts/index.yaml

I have to restrict lightbend console to a namespace. How can we achieve and i have used normal roles instead of cluster role and i dont see data feeding in to console ui.

The value of "apiVersion" in each of the deployments changes between being hard coded as, "extensions/v1beta1" and using a reference to the same value in Values.yaml (see the difference between alertmanager-deployment.yaml and es-console-deployment.yaml as examples of this). Should these all be consistent across all deployment.yaml files?

Copyright [yyyy] [name of copyright owner]

The Kubernetes cluster I am working with requires taints configuration for pod scheduling, I can't find a predefined configuration for that in values.yaml. How do I achieve this?