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

VMAgent CRD vmagent.spec.aPIServerConfig not apiServerConfig #1239

Open
liuxuzxx opened this issue Feb 17, 2025 · 1 comment
Open

VMAgent CRD vmagent.spec.aPIServerConfig not apiServerConfig #1239

liuxuzxx opened this issue Feb 17, 2025 · 1 comment
Labels
enhancement New feature or request

Comments

@liuxuzxx
Copy link

 liuxu@liuxu-B560M-AORUS-ELITE  /media/liuxu/data/code/github  kubectl explain vmagent.spec  
KIND:     VMAgent
VERSION:  operator.victoriametrics.com/v1beta1

RESOURCE: spec <Object>

DESCRIPTION:
     VMAgentSpec defines the desired state of VMAgent

FIELDS:
   aPIServerConfig	<Object>
     APIServerConfig allows specifying a host and auth methods to access
     apiserver. If left empty, VMAgent is assumed to run inside of the cluster
     and will discover API servers automatically and use the pod's CA
     certificate and bearer token file at
     /var/run/secrets/kubernetes.io/serviceaccount/.

The name of the vmagent.spec property aPIServerConfig is a bit strange. It should not be: apiServerConfig

@liuxuzxx liuxuzxx changed the title VMAgent CRD vmagent.spec.aPIServerConfig not apiVerverConfig VMAgent CRD vmagent.spec.aPIServerConfig not apiServerConfig Feb 17, 2025
@liuxuzxx
Copy link
Author

It's just that the naming feels strange, nothing else is wrong

@f41gh7 f41gh7 added the enhancement New feature or request label Feb 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants