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

Patches not applied when target.namespace is specified #5796

Open
bozho opened this issue Nov 6, 2024 · 1 comment
Open

Patches not applied when target.namespace is specified #5796

bozho opened this issue Nov 6, 2024 · 1 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.

Comments

@bozho
Copy link

bozho commented Nov 6, 2024

What happened?

I'm learning Flux, so I'm not sure if this is a Flux or a Kustomize behaviour issue (or a "me" issue :-). I'm deploying the podinfo example and trying to patch the HorizontalPodAutoscaler.

If I don't specify namespace in Flux's Kustomization spec.patches.target, the patch works. If I do specify it, it's not applied and there is no error message. Even if I specify a non-existent namespace, there is no error message.

What did you expect to happen?

The patch to be applied when target.namespace is specified.

How can we reproduce it (as minimally and precisely as possible)?

---
apiVersion: source.toolkit.fluxcd.io/v1
kind: GitRepository
metadata:
  name: podinfo
  namespace: flux-system
spec:
  interval: 1m0s
  ref:
    branch: master
  url: https://github.com/stefanprodan/podinfo
---
apiVersion: kustomize.toolkit.fluxcd.io/v1
kind: Kustomization
metadata:
  name: podinfo
  namespace: flux-system
spec:
  interval: 30m0s
  path: ./kustomize
  prune: true
  retryInterval: 2m0s
  sourceRef:
    kind: GitRepository
    name: podinfo
  targetNamespace: podinfo
  timeout: 3m0s
  wait: true
  patches:
    - target:
        name: podinfo
#        namespace: podinfo # Namespace podinfo exists.
        kind: HorizontalPodAutoscaler
      patch: |-
        apiVersion: autoscaling/v2
        kind: HorizontalPodAutoscaler
        metadata:
          name: podinfo
        spec:
          minReplicas: 2
          maxReplicas: 5

Expected output

NAMESPACE   NAME                                          REFERENCE            TARGETS              MINPODS   MAXPODS   REPLICAS   AGE
podinfo     horizontalpodautoscaler.autoscaling/podinfo   Deployment/podinfo   cpu: <unknown>/99%   2         5         2          99m

Actual output

NAMESPACE   NAME                                          REFERENCE            TARGETS              MINPODS   MAXPODS   REPLICAS   AGE
podinfo     horizontalpodautoscaler.autoscaling/podinfo   Deployment/podinfo   cpu: <unknown>/99%   2         4         2          99m

Kustomize version

5.4 (using Flux 2.4.0)

Operating system

Linux

@bozho bozho added the kind/bug Categorizes issue or PR as related to a bug. label Nov 6, 2024
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the triage/accepted label.

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.

@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Nov 6, 2024
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

No branches or pull requests

2 participants