-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Remove unused caCertSecret #16793
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove unused caCertSecret #16793
Conversation
started the job as gitpod-build-aledbf-bye-custom-ca-cert.8 because the annotations in the pull request description changed |
600e75e
to
3ea0c27
Compare
started the job as gitpod-build-aledbf-bye-custom-ca-cert.26 because the annotations in the pull request description changed |
3ea0c27
to
bca0027
Compare
started the job as gitpod-build-aledbf-bye-custom-ca-cert.30 because the annotations in the pull request description changed |
started the job as gitpod-build-aledbf-bye-custom-ca-cert.31 because the annotations in the pull request description changed |
started the job as gitpod-build-aledbf-bye-custom-ca-cert.32 because the annotations in the pull request description changed |
started the job as gitpod-build-aledbf-bye-custom-ca-cert.34 because the annotations in the pull request description changed |
/werft with-integration-tests=workspace with-large-vm=true with-gce-vm=true 👎 unknown command: with-integration-tests=workspace |
/werft run with-integration-tests=workspace with-large-vm=true with-gce-vm=true 👍 started the job as gitpod-build-aledbf-bye-custom-ca-cert.35 |
started the job as gitpod-build-aledbf-bye-custom-ca-cert.36 because the annotations in the pull request description changed |
started the job as gitpod-build-aledbf-bye-custom-ca-cert.37 because the annotations in the pull request description changed |
/werft run with-integration-tests=workspace with-large-vm=true with-gce-vm=true 👍 started the job as gitpod-build-aledbf-bye-custom-ca-cert.39 |
started the job as gitpod-build-aledbf-bye-custom-ca-cert.54 because the annotations in the pull request description changed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The combination of installer and application level changes make this PR more difficult to review. An approach to make that easier is to first update/remove from the installer, and then make the application level changes. This also ensures that we can do an install in between (with just installer config changes) without actually removing the app code. That in turn can make our life easier should we need to revert this.
@@ -180,6 +180,23 @@ function installFluentBit { | |||
upgrade --install fluent-bit fluent/fluent-bit --version 0.21.6 -n "${PREVIEW_NAMESPACE}" -f "$ROOT/.werft/vm/charts/fluentbit/values.yaml" | |||
} | |||
|
|||
function installTrustManager { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How is this change related to this PR?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To be able to get a workspace preview running after running the installer
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, I don't follow. What in this PR makes it so that we now have to install the trust manager which we didn't need before?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The new Bundle definitions solve the issues we have right an invalid cert-manager CA, certificate rotation, and complexity to update /etc/ssl/ca-certificates.crt
I can't do that here. If I only remove the feature without fixing the CA state, we break registry-facade (in particular) |
Signed-off-by: Manuel de Brito Fontes <[email protected]>
Signed-off-by: Manuel de Brito Fontes <[email protected]>
Signed-off-by: Manuel de Brito Fontes <[email protected]>
4c02380
to
35b75c3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, tested in a preview env starting a workspace and an image build
Description
Remove an unused feature that also creates an invalid configuration in
registry-facade
.It also introduces trust-manager to centralize and simplify the management of
ca-certificate.crt
in the componentsIf in the future we need to add support for a custom CA certificate, we only need to add a reference to a secret in the bundle
How to test
Related issues
fixes #16767
Release Notes
Build Options:
Run the build with werft instead of GHA
leeway-target=components:all
Run Leeway with
--dont-test
Publish Options
Installer Options
Add desired feature flags to the end of the line above, space separated
Preview Environment Options:
If enabled this will build
install/preview
If enabled this will create the environment on GCE infra
Valid options are
all
,workspace
,webapp
,ide
,jetbrains
,vscode
,ssh