Added
- Adding
opsctl login
support for EKS clusters.
opsctl login
support for EKS clusters.--login-timeout
flag to control the time period of OIDC login timeoutcluster-eks
with provider eks
.login
command in case workload cluster API is not known--cluster-admin
flag in the login
command--cluster-config
and --default-app-config
parameters which required handcrafted YAML input. It leaves one consistent templating option for CAPI products (kubectl gs template cluster --provider ... --other-params
).sig.k8s.io/yam@v1.3.0
template nodepool
.spec.config.configMap
in app/<cluster-name>-default-apps
for CAPZ
clusters.--proxy
and --proxy-port
flags to login cmd
to enable proxy-url: socks5://localhost:9000
in the cluster section of the configuration added to kubeconfigclientcert
Workload Clustersv1alpha3
version when using CAPI CRDs.kubectl gs template cluster
now by default creates a node pool with the name nodepool0
, instead of machine-pool0
, as the latter is no longer valid according to the cluster-aws schema as of v0.24.0.cluster template
supports a generic way to template CAPI
based clusters where all the input parameters are given as values.yaml
from the corresponding cluster
and default-apps
chart.CAPZ
implementation and switched to the generic templating implementation.kubectl gs template cluster
for Cluster API provider AWS has been adapted to work with the values schema of cluster-aws v0.28.0.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.