Skip to content
This repository has been archived by the owner on Apr 25, 2023. It is now read-only.

KubeFedConfig scope should be immutable #1058

Closed
font opened this issue Jul 26, 2019 · 0 comments · Fixed by #1062
Closed

KubeFedConfig scope should be immutable #1058

font opened this issue Jul 26, 2019 · 0 comments · Fixed by #1062
Assignees
@font
Labels
kind/bug Categorizes issue or PR as related to a bug.
Milestone
v0.1.0

Comments

@font
Copy link
Contributor

font commented Jul 26, 2019

What happened:
Modifying the kubefed KubeFedConfig scope from Cluster to Namespaced succeeded.

What you expected to happen:
Validation failure suggesting the field is immutable.

How to reproduce it (as minimally and precisely as possible):

  1. deploy cluster-scoped kubefed
  2. modify the scope in the kubefed KubeFedConfig to Namespaced

Anything else we need to know?:
See #916 for more details.

Environment:

  • Kubernetes version (use kubectl version): v1.14.2
  • KubeFed version: v0.1.0-rc4
  • Scope of installation (namespaced or cluster): cluster
  • Others

/kind bug
@font font added this to the v0.1.0 milestone Jul 26, 2019
@k8s-ci-robot k8s-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Jul 26, 2019
@font font self-assigned this Jul 29, 2019
@font font mentioned this issue Jul 29, 2019
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@font font

Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Milestone
v0.1.0
Development

Successfully merging a pull request may close this issue.

Make KubeFedConfig scope immutable font/kubefed
2 participants
@font @k8s-ci-robot