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

yaml feature not support #4311

Closed
pythonwood opened this issue Nov 27, 2021 · 2 comments
Closed

yaml feature not support #4311

pythonwood opened this issue Nov 27, 2021 · 2 comments
Labels
area/anchors related to yaml anchors kind/bug Categorizes issue or PR as related to a bug. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@pythonwood
Copy link

Files that can reproduce the issue

version: 4.4.1

 resources:                                                                                                              
   - a.yaml
# a.yaml
---
kind: Ingress
apiVersion: networking.k8s.io/v1
metadata:
  name: a-ingress
spec:
  tls:
  - hosts:
      - "*.abc.com"
      - abc.com
    secretName: abc.com
  rules:
  - host: api1.abc.com
    http: &http
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: svc202111
            port:
              number: 2021
  # kustomize build . not support below , annote it with work
  - host: api2.abc.com
    http:
      <<: *http

however, kubectl apply -f a.yaml just ok

Expected output

Actual output

error: map[string]interface {}{"apiVersion":"networking.k8s.io/v1", "kind":"Ingress", "metadata":map[string]interface {}{"name":"..... json: unsupported type: map[interface {}]interface {}

Kustomize version

version: 4.4.1

Platform

Additional context

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

@pythonwood: 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/test-infra 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 27, 2021
@natasha41575 natasha41575 added area/anchors related to yaml anchors triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Dec 30, 2021
@KnVerey
Copy link
Contributor

KnVerey commented Mar 23, 2022

Duplicate of #4215 , closed by #4383

@KnVerey KnVerey closed this as completed Mar 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/anchors related to yaml anchors kind/bug Categorizes issue or PR as related to a bug. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

4 participants