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
This is due being unable to apply v1beta1.platformadmins CRD due to kubectl.kubernetes.io/last-applied-configuration being stored as metadata in the update.
k apply -f iot.openyurt.io_platformadmins.yaml
Warning: resource customresourcedefinitions/platformadmins.iot.openyurt.io is missing the kubectl.kubernetes.io/last-applied-configuration annotation which is required by kubectl apply. kubectl apply should only be used on resources created declaratively by either kubectl create --save-config or kubectl apply. The missing annotation will be patched automatically.
The CustomResourceDefinition "platformadmins.iot.openyurt.io" is invalid: metadata.annotations: Too long: must have at most 262144 bytes
@ssen85 when you install yurt-manager, you can pass a values.yaml file with controllers: "-nodelifecycle,-platformadmin,*" set to disable the platformadmin controller.
helm upgrade --install yurt-manager -n kube-system openyurt/yurt-manager -f values.yaml per the docs
What happened:
yurt-manager cannot start.
logs:
How to reproduce it (as minimally and precisely as possible):
Install openyurt 1.6.0 in k8s 1.30.8.
Environment:
kubectl version
): 1.30.8cat /etc/os-release
): almalinux 9.5uname -a
): 5.14.0-503.19.1.el9_5.x86_64/kind bug
The text was updated successfully, but these errors were encountered: