You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cluster API should clearly document and test bring-your-own-cert use cases for KCP. A change in v1.5 requiring generated certs to have the cluster.x-k8s.io/cluster-name=${CLUSTER_NAME} label is not fully documented.
#9080 added documentation for the kubeconfig - but it should be updated to make clear that this also applies to all other secrets generated for KCP. This change should be backported to release-1.5.
We should also add a test - an integration test if possible showing the failing and non-failing cases - so we can prevent regressions in this behaviour in future.
Cluster API should clearly document and test bring-your-own-cert use cases for KCP. A change in v1.5 requiring generated certs to have the
cluster.x-k8s.io/cluster-name=${CLUSTER_NAME}
label is not fully documented.#9080 added documentation for the kubeconfig - but it should be updated to make clear that this also applies to all other secrets generated for KCP. This change should be backported to
release-1.5
.We should also add a test - an integration test if possible showing the failing and non-failing cases - so we can prevent regressions in this behaviour in future.
h/t @lentzi90 for reporting this. Reference slack thread..
The text was updated successfully, but these errors were encountered: