Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot start CAPI providers restricted to a namespace #624

Open
serngawy opened this issue Oct 15, 2024 · 1 comment · May be fixed by #625
Open

Cannot start CAPI providers restricted to a namespace #624

serngawy opened this issue Oct 15, 2024 · 1 comment · May be fixed by #625
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@serngawy
Copy link

What steps did you take and what happened:
create infrastructure Provider ex; CAPA with setting the container manager args to include a namespace

apiVersion: operator.cluster.x-k8s.io/v1alpha2
kind: InfrastructureProvider
metadata:
  name: aws
  namespace: capa-system
spec:
  configSecret:
    name: capa-manager-bootstrap-credentials
    namespace: capa-system
  deployment:
    containers:
      - command:
          - /manager
        args:
          "--namespace": "capa-system"
        name: manager
  version: v2.6.1

What did you expect to happen:
Expect to have the capa provider deployment args assigned with "--namespace"

Anything else you would like to add:
Found the check for the provider args here ignoring the namespace as argument.

Environment:

  • Cluster-api-operator version: 0.14.0
  • Cluster-api version: 1.8.2
  • Minikube/KIND version:
  • Kubernetes version: (use kubectl version): version.Info{Major:"1", Minor:"29", Compiler:"gc", Platform:"linux/amd64"}
  • OS (e.g. from /etc/os-release):

/kind bug
[One or more /area label. See https://github.com/kubernetes-sigs/cluster-api-operator/labels?q=area for the list of labels]

@k8s-ci-robot k8s-ci-robot added kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Oct 15, 2024
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If CAPI Operator contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@serngawy serngawy linked a pull request Oct 15, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants