Can not add any comment in .yaml

[Jojoooo1]

Describe the bug
Can not add a comment in my .yaml

Trying to use kustomize with a .yaml using a comment.
Version 3.8.10 works perfectly
Version 3.9.3 throw yaml: invalid trailing UTF-8 octet

Files that can reproduce the issue

kustomization.yaml

apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization

namespace: default

resources:
  - ingress.yaml

ingress.yaml

apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
  name: ingress-intelipoint
spec:
  rules:
    - host: # A COMMENT
      http:
        paths:
          - backend:
              serviceName: intelipoint-api
              servicePort: 80

Expected output

apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
  name: ingress-intelipoint
  namespace: default
spec:
  rules:
    - host:
      http:
        paths:
          - backend:
              serviceName: intelipoint-api
              servicePort: 80

Actual output

Error: map[string]interface {}{"apiVersion":"networking.k8s.io/v1beta1", "kind":"Ingress", "metadata":map[string]interface {}{"annotations":map[string]interface {}{"cert-manager.io/cluster-issuer":"letsencrypt-prod", "kubernetes.io/ingress.class":"nginx", "nginx.ingress.kubernetes.io/force-ssl-redirect":"true"}, "name":"ingress-intelipoint", "namespace":"default"}, "spec":map[string]interface {}{"rules":[]interface {}{map[string]interface {}{"host":interface {}(nil), "http":map[string]interface {}{"paths":[]interface {}{map[string]interface {}{"backend":map[string]interface {}{"serviceName":"intelipoint-api", "servicePort":80}}}}}}}}: yaml: invalid trailing UTF-8 octet

Kustomize version

{Version:kustomize/v3.9.3 GitCommit:1ae8303bdc9372bc7c15942df6e9cf5d67fdba1a BuildDate:2021-02-07T17:02:13Z GoOs:linux GoArch:amd64}

Platform

Ubuntu 18.04.5 LTS

Edit: work by using kustomize build . --enable_kyaml=false

[cfraenkel]

I'm hitting the same error, but only when the comment contains a non ascii unicode character like 'ä'.

apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
  name: ingress-intelipoint
spec:
  rules:
    - host: # Ä COMMENT
      http:
        paths:
          - backend:
              serviceName: intelipoint-api
              servicePort: 80

if the unicode char appears in a non-comment there is no similar error:

apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
  name: ingress-intelipoint
spec:
  rules:
    - host: ä # A COMMENT
      http:
        paths:
          - backend:
              serviceName: intelipoint-api
              servicePort: 80

This issue also affects the kustomize bundled in the most recent kubectl 1.21.0

Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.0", GitCommit:"cb303e613a121a29364f75cc67d3d580833a7479", GitTreeState:"clean", BuildDate:"2021-04-08T16:31:21Z", GoVersion:"go1.16.1", Compiler:"gc", Platform:"linux/amd64"}

[Shell32-Natsu]

This issue is in go-yaml library and we need to update it. #3789 does this and this should be fixed after it.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

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.