Highlights for the week ending October 20, 2022
User interfaces
- kubectl-gs v2.25.0 fixes a problem in
kubectl gs login
with--self-contained
, where modifications to an existing file failed.
Apps
- dex-app v1.30.0 provides Dex v2.35.3.
kubectl gs login
with --self-contained
, where modifications to an existing file failed.kubectl-gs v2.24.2 fixes several problems with kubectl gs login
:
The customer cluster admin group and default:automation
service account have now access to Flux logs for debugging issues with the Flux system.
flux-app version v0.16.0 upgrades to support Flux toolkit v0.35.0. Breaking changes: from Flux v0.34.0 onward, Flux controller logs have been aligned with the Kubernetes structured logging, further details here. From Flux v0.35.0, strict validation rules have been put in place for API fields which define a time duration, so values without a time unit (e.g. ms
, s
, m
, h
) will now be rejected by the API server.
The kubectl gs login
command as of v2.23.0 provides a flag --cn-prefix
. This allows to specify the CN of a client certificate issued for workload cluster access, so that the client using the certificate can be mapped to RBAC rules which are bound to a user.
giantswarm
catalog. It will be removed from the playground
catalog in a future release.ReportChangeRequest
resources when they exceed a configured threshold.CISKubeBenchReports
by default in support of the switch to Trivy Operator.0.30.4
.0.2.1
, adding support for calling custom webhooks and exposing more configuration options for scan jobs.You’ll now find information about our Cluster API architecture in our docs.
As of the latest version, our web UI is ready for use on Google Cloud Platform (GCP) installations.
kubectl-gs v2.23.0 adds the capability to create a client certificate for workload cluster access with a specific CN prefix. This means you can bind the client presenting this certificate to an RBAC role as a user. Check the login
command’s new --cn-prefix
flag.
We now have a dedicated page clarifying the concept and value of app bundles and its place in the app platform.
In kubectl-gs we have deprecated some flags in three commands, to avoid name conflicts with global flags (which are usable in all commands). You will see a warning when using the deprecated flags. This affects the following commands:
kubectl gs template app
: flag --target-namespace
replaces --namespace
, --cluster-name
replaces --cluster
.kubectl gs template catalog
: flag --target-namespace
replaces --namespace
.kubectl gs gitops add app
: flag --target-namespace
replaces --namespace
.Please move any scripts to the new flags, as the old flags will change their meaning with the next major release of kubectl-gs.
kubectl-gs now also provides a command get organizations
, which is a way for all management API users to list the organizations they have access to. kubectl get organizations
in contrast requires admin permissions.
configmap.use-proxy-protocol
by default for AWS. Before this was achieved by cluster-operator
setting configmap.use-proxy-protocol
in the cluster values.0.29.2
, introducing support for Trivy modules. The spring4shell
module is installed by default.We added the Documentation on how to package custom dashboards together with apps instead of packaging them into a custom repository.
All management-cluster Flux installations (flux-system
, flux-giantswarm
) have been upgraded to Flux v0.33.0.
We have created the first v0.1.0 release of our gitops-template repo. It includes now all examples showing how to use our GitOps offering to achieve functionality such as management of organizations, workload clusters, secrets encryption, preparing and using app and cluster templates, environments propagation. To make it easier to use, we’re also introducing a new set of commands to our kubectl gs
plugin that will allow you to easily generate parts of the GitOps configuration instead of just copying and changing it.
trivy-operator
as the upcoming replacement for starboard
. It also includes the latest Kyverno app release (v0.11.1).trivy-operator
containing upstream version 0.1.0. We recommend starboard
users use this release to assess their readiness to migrate to trivy-operator
.We fixed a problem in our web UI that has prevented some non-admin users from logging in. In addition, in the list of apps installed in a cluster, it is now easier to spot the ones that are not in the expected “Deployed” state.
v0.13.0
. We added important installation notes to the project’s README.md to clarify the benefits and limitations of this approach. We recommend skipping v0.13.0
and use v0.14.0
instead.Starting today, our weekly product highlights will reach you on Thursday already. That, of course, does not mean that our work week is already over.
kyverno-app version v0.11.1 updates policy-reporter
and included UIs to version 2.11.1 and sets additional configuration for improving Kyverno’s resilience against rate limiting.
nginx-ingress-controller-app version v2.16.0 updates to upstream controller version v1.3.0, removes support for kubernetes v1.19.0 and increases default replica number to 2.
For apps installed in a workload cluster, the web UI now shows the name of the App resource (in case it’s not identical with the app’s name in the catalog). This makes it easier to distinguish several apps of the same type, e. g. if you have NGINX Ingress controller installed multiple times.
We also improved the display of an App resources’ deployment status.
kubectl-gs since version 2.19.0 consistently supports flags related to the kubectl config in all commands, including --kubeconfig
for the path to a config file, --context
for selecting a context, --cluster
, --user
etc.
We added documentation on how to use cert-manager to automatically obtain TLS certificates for ingresses.
This part of our documentation refers to our vintage product. The content may be not valid anymore for our current product. Please check our new documentation hub for the latest state of our docs.