8000 Installation via `kubectl apply --server-side` fails on subsequent runs · Issue #6824 · kedacore/keda · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Installation via kubectl apply --server-side fails on subsequent runs #6824
@jgaskins

Description

@jgaskins

Report

Deploying from the YAML files based on the docs:

kubectl apply --server-side -f https://github.com/kedacore/keda/releases/download/v2.17.1/keda-2.17.1.yaml

Works the first time, fails the second time.

Expected Behavior

The second invocation of the kubectl apply --server-side command would update — kubectl apply is usually idempotent.

Actual Behavior

Output

namespace/keda serverside-applied
customresourcedefinition.apiextensions.k8s.io/cloudeventsources.eventing.keda.sh serverside-applied
customresourcedefinition.apiextensions.k8s.io/clustercloudeventsources.eventing.keda.sh serverside-applied
customresourcedefinition.apiextensions.k8s.io/clustertriggerauthentications.keda.sh serverside-applied
customresourcedefinition.apiextensions.k8s.io/scaledjobs.keda.sh serverside-applied
customresourcedefinition.apiextensions.k8s.io/scaledobjects.keda.sh serverside-applied
customresourcedefinition.apiextensions.k8s.io/triggerauthentications.keda.sh serverside-applied
serviceaccount/keda-operator serverside-applied
role.rbac.authorization.k8s.io/keda-operator serverside-applied
clusterrole.rbac.authorization.k8s.io/keda-external-metrics-reader serverside-applied
clusterrole.rbac.authorization.k8s.io/keda-operator serverside-applied
rolebinding.rbac.authorization.k8s.io/keda-operator serverside-applied
rolebinding.rbac.authorization.k8s.io/keda-auth-reader serverside-applied
clusterrolebinding.rbac.authorization.k8s.io/keda-hpa-controller-external-metrics serverside-applied
clusterrolebinding.rbac.authorization.k8s.io/keda-operator serverside-applied
clusterrolebinding.rbac.authorization.k8s.io/keda-system-auth-delegator serverside-applied
service/keda-admission-webhooks serverside-applied
service/keda-metrics-apiserver serverside-applied
service/keda-operator serverside-applied
deployment.apps/keda-admission serverside-applied
deployment.apps/keda-metrics-apiserver serverside-applied
deployment.apps/keda-operator serverside-applied
apiservice.apiregistration.k8s.io/v1beta1.external.metrics.k8s.io serverside-applied
error: Apply failed with 6 conflicts: conflicts with "admissionsenforcer" using admissionregistration.k8s.io/v1:
- .webhooks[name="vcloudeventsource.kb.io"].namespaceSelector
- .webhooks[name="vclustercloudeventsource.kb.io"].namespaceSelector
- .webhooks[name="vscaledjob.kb.io"].namespaceSelector
- .webhooks[name="vscaledobject.kb.io"].namespaceSelector
- .webhooks[name="vsclustertriggerauthentication.kb.io"].namespaceSelector
- .webhooks[name="vstriggerauthentication.kb.io"].namespaceSelector
Please review the fields above--they currently have other managers. Here
are the ways you can resolve this warning:
* If you intend to manage all of these fields, please re-run the apply
  command with the `--force-conflicts` flag.
* If you do not intend to manage all of the fields, please edit your
  manifest to remove references to the fields that should keep their
  current managers.
* You may co-own fields by updating your manifest to match the existing
  value; in this case, you'll become the manager if the other manager(s)
  stop managing the field (remove it from their configuration).
See https://kubernetes.io/docs/reference/using-api/server-side-apply/#conflicts

Steps to Reproduce the Problem

Running on Azure Kubernetes Service

Run this command twice:

kubectl apply --server-side -f https://github.com/kedacore/keda/releases/download/v2.17.1/keda-2.17.1.yaml

Logs from KEDA operator

No response

KEDA Version

2.17.0

Kubernetes Version

1.31

Platform

Other

Scaler Details

Prometheus

Anything else?

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    Status

    To Triage

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0