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
What happened?
Some kubernetes applications need to use a server-side apply to circumvent API limitations, most notably the annotations field being longer than 262144 bytes, which might happen when you apply CRDs. For example, applying the cloud native postgres operator (cnpg) requires a server-side apply.
Though we have the possibility to add --server-side in the applyArgs, this flag is incompatible with the --force flag, which is used by default, failing the devspace dev command.
I received the following output:
info Using namespace 'my-project'
info Using kube context 'rancher-desktop'
my-project deploy:cnpg Applying manifests with kubectl...
my-project deploy:cnpg error: --force cannot be used with --server-side
my-project create_deployments: error deploying cnpg: error: --force cannot be used with --server-side
my-project error executing 'kubectl --context rancher-desktop apply --force -f - --server-side':
my-project Please make sure the command `kubectl apply` does work locally with manifest `https://raw.githubusercontent.com/cloudnative-pg/cloudnative-pg/release-1.23/releases/cnpg-1.23.1.yaml`
What did you expect to happen instead?
I would like to use a server-side apply when I set --server-side flag.
How can we reproduce the bug? (as minimally and precisely as possible)
What happened?
Some kubernetes applications need to use a server-side apply to circumvent API limitations, most notably the annotations field being longer than 262144 bytes, which might happen when you apply CRDs. For example, applying the cloud native postgres operator (cnpg) requires a server-side apply.
Though we have the possibility to add
--server-side
in theapplyArgs
, this flag is incompatible with the--force
flag, which is used by default, failing the devspace dev command.I received the following output:
What did you expect to happen instead?
I would like to use a server-side apply when I set
--server-side
flag.How can we reproduce the bug? (as minimally and precisely as possible)
My devspace.yaml:
Local Environment:
Kubernetes Cluster:
Client Version: v1.28.9
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.28.4+k3s2
Anything else we need to know?
The text was updated successfully, but these errors were encountered: