feat(helm)!: Update chart kubernetes-dashboard to 7.4.0 #384
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
6.0.8
->7.4.0
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
kubernetes/dashboard (kubernetes-dashboard)
v7.4.0
Compare Source
General-purpose web UI for Kubernetes clusters
v7.3.2
Compare Source
What's Changed
API
Helm Chart
Full Changelog: kubernetes/dashboard@kubernetes-dashboard-7.3.1...kubernetes-dashboard-7.3.2
Installation
Compatibility
✓
Fully supported version range.?
Due to breaking changes between Kubernetes API versions, some features might not work correctly in the Dashboard.Images
v7.3.1
Compare Source
What's Changed
Full Changelog: kubernetes/dashboard@kubernetes-dashboard-7.3.0...kubernetes-dashboard-7.3.1
Installation
Compatibility
✓
Fully supported version range.?
Due to breaking changes between Kubernetes API versions, some features might not work correctly in the Dashboard.Images
v7.3.0
Compare Source
What's Changed
Helm Chart
Full Changelog: kubernetes/dashboard@kubernetes-dashboard-7.2.0...kubernetes-dashboard-7.3.0
Installation
Compatibility
✓
Fully supported version range.?
Due to breaking changes between Kubernetes API versions, some features might not work correctly in the Dashboard.Images
v7.2.0
Compare Source
What's Changed
API
Helm Chart
It will no longer be regenerated on every helm run. Instead, it will use a lookup function to make sure that the
private.key
value is not empty. If secret will be deleted or key changed, then checksum annotation on api/auth containers will trigger a rollout restart.dns_order
configuration to include experimentalAAAA
record for ipv6 lookup. It can potentially fix issues with accessing Dashboard on IPv6-enabled cluster. Closes #88551.4.1
New Contributors
Full Changelog: kubernetes/dashboard@kubernetes-dashboard-7.1.3...kubernetes-dashboard-7.2.0
Installation
Compatibility
✓
Fully supported version range.?
Due to breaking changes between Kubernetes API versions, some features might not work correctly in the Dashboard.Images
v7.1.3
Compare Source
What's Changed
API
Web
Helm Chart
kong_dns_order
entry in an attempt to mitigate latency issuesNew Contributors
Full Changelog: kubernetes/dashboard@kubernetes-dashboard-7.1.2...kubernetes-dashboard-7.1.3
Installation
Compatibility
✓
Fully supported version range.?
Due to breaking changes between Kubernetes API versions, some features might not work correctly in the Dashboard.Images
v7.1.2
Compare Source
What's changed
Full Changelog: kubernetes/dashboard@kubernetes-dashboard-7.1.1...kubernetes-dashboard-7.1.2
Helm Chart
1.3.0
Installation
Compatibility
✓
Fully supported version range.?
Due to breaking changes between Kubernetes API versions, some features might not work correctly in the Dashboard.Images
v7.1.1
Compare Source
What's changed
Full Changelog: kubernetes/dashboard@auth/v1.1.1...kubernetes-dashboard-7.1.1
Auth
/api/v1/me
endpoint with username and as an information if user was correctly authenticatedWeb
/me
endpointHelm Chart
/me
endpoint routingInstallation
Compatibility
✓
Fully supported version range.?
Due to breaking changes between Kubernetes API versions, some features might not work correctly in the Dashboard.Images
v7.1.0
Compare Source
What's changed
Full Changelog: kubernetes/dashboard@kubernetes-dashboard-7.0.1...kubernetes-dashboard-7.1.0
Helm chart
Installation
Compatibility
✓
Fully supported version range.?
Due to breaking changes between Kubernetes API versions, some features might not work correctly in the Dashboard.Images
v7.0.1
Compare Source
What's changed
Full Changelog: kubernetes/dashboard@web/v1.2.1...kubernetes-dashboard-7.0.1
Web container
Helm chart
Installation
Compatibility
✓
Fully supported version range.?
Due to breaking changes between Kubernetes API versions, some features might not work correctly in the Dashboard.Images
v7.0.0
Breaking change
This release introduces a couple of important changes to how Kubernetes Dashboard generally works. It requires clean installation.API container
It is now fully stateless, meaning it does not rely on Kubernetes resources to run. It will always require an authorization token to be present to authorize the request. It is no longer possible for the API container to use its own SA privileges to skip authorization. All arguments that were frontend specific have either been removed or moved to the Web container.
csrf-key
argument - Base64 encoded random 256 bytes key. Can be loaded fromCSRF_KEY
environment variable.Auth container
Authentication logic is now handled by the new dashboard auth container. Currently, it only exposes
/login
endpoint. We will also add support for OIDC with OAuth flow and/me
endpoint in the future.csrf-key
argument - Base64 encoded random 256 bytes key. Can be loaded fromCSRF_KEY
environment variable.Web container
Go backend
restful-go
withgin
as main web frameworkAngular frontend
Since API requires from the user to always provide
Authorization: Bearer <token>
now, there is no way to skip login and act as a Dashboard.token
on the login screenskip
login optionKong gateway
Since the number of our containers is growing as we split parts of the logic, we have decided to use a gateway that will connect all of them and ensure the Dashboard is working properly. There were a couple of reasons to choose Kong:
It will now be a required dependency that we use to expose the Dashboard. Users can then reconfigure it or use another proxy in front of it. It will simply act as a single point when accessing the Kubernetes Dashboard.
Metrics scraper
sqlite
Go dependency to used driver implementation that does not requireCGO_ENABLED=1
during the build. It is a pure Go implementation.Helm chart
This is a complete overhaul of the helm chart. It includes:
app.ingress.useDefaultAnnotations=false
ingressClassName
can now be skipped from spec and it should fallback to using default ingress class (if configured). It is controlled byapp.ingress.useDefaultIngressClass
.app.mode=api
kong.enabled=false
api.containers.args={--metrics-provider=none}
cert-manager
,nginx
andmetrics-server
are now disabled by default. Onlykong
dependency is required.clusterReadOnlyRole
has been removed since it is no longer possible to use Dashboard permissions to access the cluster. User access is required at all times.Installation
Compatibility
✓
Fully supported version range.?
Due to breaking changes between Kubernetes API versions, some features might not work correctly in the Dashboard.Images
What's Changed
Full Changelog: kubernetes/dashboard@v3.0.0-alpha0...kubernetes-dashboard-7.0.0
Configuration
📅 Schedule: Branch creation - "on saturday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.