-
Notifications
You must be signed in to change notification settings - Fork 55
[WIP] Add hpa annotations #285
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
[WIP] Add hpa annotations #285
Conversation
Is it really easier / less risky to read and write these annotations instead just using the |
Is a great question. ATM I'm just working out reading them to test for the API & notify the user to go edit the HPA via cli. I think if we wanted to write them, we should def update to the next version instead. |
return (icon) ? icon : "fa fa-cube"; | ||
}; | ||
}); | ||
return function(resource, /* optional */ tagName) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All I'm using this for is https://github.com/openshift/origin-web-console/pull/2708/files#diff-04a314c1b6d2d3fc082233f2ee89fa0cR106, reading, not writing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@spadgett ping, objections? I'm not setting anything, this is just used to get at the annotations. I could inline a similar fn, but figured this is where it should live.
I'll close this out per the |
…w-api-warning Automatic merge from submit-queue. hpa v2beta1 api warning on DC & edit autoscaler pages This PR depends on [common 285](openshift/origin-web-common#285). [WIP] notes: `bower link origin-web-common` with the above PR or the tests will fail. On the DC page:  - probably only want to show the v2beta1 message, will hide the other On the edit autoscaler page:  - shows a message w/a link to CLI - hides the CPU request input as editing this is probably not what the user wants to do TODO (perhaps follow-on PR): - Update the warning message to show the user the data from the `metrics` annotation so they can easily see what the autoscaler is using to scale the resource.
HPA
v2beta1
requested fromv1
api will have these annotations.@jwforres @spadgett