chore: update NOTES.txt to remove metrics access instructions
- Removed instructions for accessing metrics via port-forwarding as metrics are no longer enabled by default. - This change simplifies the deployment notes for the secret operator. Signed-off-by: zhenyus <zhenyus@mathmast.com>
This commit is contained in:
parent
54d82ac690
commit
6f7dde476f
@ -17,13 +17,6 @@ The operator has been deployed with the following configuration:
|
|||||||
- Debug mode: {{ .Values.operator.debug }}
|
- Debug mode: {{ .Values.operator.debug }}
|
||||||
- API Server Port: {{ .Values.operator.apiServerPort }}
|
- API Server Port: {{ .Values.operator.apiServerPort }}
|
||||||
|
|
||||||
{{- if .Values.metrics.enabled }}
|
|
||||||
|
|
||||||
Metrics are enabled and can be accessed via service:
|
|
||||||
$ kubectl port-forward svc/{{ include "freeleaps-secret-operator.fullname" . }}-metrics {{ .Values.metrics.service.port }}:{{ .Values.metrics.service.port }}
|
|
||||||
Then visit http://localhost:{{ .Values.metrics.service.port }}/metrics
|
|
||||||
{{- end }}
|
|
||||||
|
|
||||||
{{- if .Values.azureKeyVault.createSecret }}
|
{{- if .Values.azureKeyVault.createSecret }}
|
||||||
|
|
||||||
Azure Key Vault configuration has been created as a Kubernetes Secret.
|
Azure Key Vault configuration has been created as a Kubernetes Secret.
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user