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

Unnecesary empty apiGroup on HelmChart #6851

Open
jorgemoralespou opened this issue Mar 13, 2024 · 3 comments
Open

Unnecesary empty apiGroup on HelmChart #6851

jorgemoralespou opened this issue Mar 13, 2024 · 3 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@jorgemoralespou
Copy link

Describe the bug:
There's 3 resources in the Helm chart that have an empty apiGroup defined that is not needed and removed when applied to the cluster.

All other references to subjects.ServiceAccount in any RoleBinding or ClusterRoleBinding are ok and don't have this empty apiGroup.

Expected behaviour:
It'll be better if these were not provided.

Environment details::

  • Kubernetes version: 1.29
  • cert-manager version: v1.14.4

/kind bug

@jetstack-bot jetstack-bot added the kind/bug Categorizes issue or PR as related to a bug. label Mar 13, 2024
@inteon inteon removed the kind/bug Categorizes issue or PR as related to a bug. label Mar 18, 2024
@inteon
Copy link
Member

inteon commented Mar 18, 2024

/kind feature

@jetstack-bot jetstack-bot added the kind/feature Categorizes issue or PR as related to a new feature. label Mar 18, 2024
@hawksight
Copy link
Member

@jorgemoralespou does the existence of this apiGroup key cause a "diff" when applying these resources through a GitOps tool?

Or is it simply just cleaner to remove the redundant lines?

@jorgemoralespou
Copy link
Author

It does, since Kubernetes (at least version 1.29) does remove these fields on the server side, and hence there's always diff when applying this in a GitOps way

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

4 participants