-
Notifications
You must be signed in to change notification settings - Fork 153
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
Possibility to target VMuser
on VLogs
#1241
Comments
Did you try it with the latest v0.53.0 release https://github.com/VictoriaMetrics/operator/releases/tag/v0.53.0? It's required to perform CRD definitions update. |
Hi @f41gh7 I use latest version Issue can be closed. |
Hi @f41gh7 , I updated CRD,operator version is 0.53.0 and the problem is still with me apiVersion: apiextensions.k8s.io/v1
kind: CustomResourceDefinition
metadata:
annotations:
controller-gen.kubebuilder.io/version: v0.16.5
helm.sh/resource-policy: keep
meta.helm.sh/release-name: vm
meta.helm.sh/release-namespace: vm
creationTimestamp: "2025-01-29T10:50:52Z"
generation: 2
labels:
app.kubernetes.io/instance: vm
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/name: victoria-metrics-operator
app.kubernetes.io/version: v0.53.0
helm.sh/chart: victoria-metrics-operator-0.42.0
helm.toolkit.fluxcd.io/name: vm
helm.toolkit.fluxcd.io/namespace: vm
name: vmusers.operator.victoriametrics.com
resourceVersion: "301598206"
uid: 3068f23b-ff70-47f0-993c-186cfa78ad5d
spec:
conversion:
strategy: None
group: operator.victoriametrics.com
names:
kind: VMUser
listKind: VMUserList
plural: vmusers
singular: vmuser
|
At the moment such a design is not possible
and I have to use this.
The text was updated successfully, but these errors were encountered: