-
Notifications
You must be signed in to change notification settings - Fork 106
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
Better Naming for Monitors #453
Labels
kind/enhancement
New feature or request
Comments
This issue is stale because it has been open for 60 days with no activity. |
This issue was closed because it has been inactive for 30 days since being marked as stale. |
Reopening issues that inadvertently were closed as stale |
This issue is stale because it has been open for 60 days with no activity. |
This issue was closed because it has been inactive for 30 days since being marked as stale. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At the moment the name of the monitor gets picked up from the name of the EndpointMonitor resource. The Metadata.Name part of the resource is limited to
a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.'
. This makes the names of the monitors look not so great. With the old annotation way of automating creating monitors there was an annotationmonitor.stakater.com/name:
where you could spacify the name you wanted and you could use spaces and capital letters.I've looked around but I can't seem to find anything similar within the EndpointMonitor resource definition. Is there even a way right now to specify the name of the monitor?
The text was updated successfully, but these errors were encountered: