Chart Version: Incremented the chart version from 0.63.0 to 0.64.0 in charts/hub/Chart.yaml. This follows Semantic Versioning and reflects the updates and improvements made in this release. Keeping the version updated ensures clarity in tracking changes and deploying the correct version.
Ingress Name Changes:
Purpose: The ingress names have been made more descriptive to avoid confusion and potential conflicts.
Changes:
In charts/hub/templates/kerberos-hub/hub-api.yaml: Changed the ingress name from oauth2-proxy to oauth2-proxy-api.
In charts/hub/templates/kerberos-hub/hub-frontend-demo.yaml: Changed the ingress name from oauth2-proxy to oauth2-proxy-frontend-demo.
In charts/hub/templates/kerberos-hub/hub-frontend.yaml: Changed the ingress name from oauth2-proxy to oauth2-proxy-frontend.
Benefits: These changes make the ingress names more specific to their respective components, improving readability and maintainability of the code. It also helps in better management and debugging of ingress resources in the Kubernetes environment.
Overall, these changes enhance the project's version management and improve the clarity and specificity of ingress resource naming, contributing to a more robust and maintainable codebase.
Pull Request Description
Title: Update to 0.64.0 + Change Ingress Names
Motivation and Improvement:
Version Update:
0.63.0
to0.64.0
incharts/hub/Chart.yaml
. This follows Semantic Versioning and reflects the updates and improvements made in this release. Keeping the version updated ensures clarity in tracking changes and deploying the correct version.Ingress Name Changes:
charts/hub/templates/kerberos-hub/hub-api.yaml
: Changed the ingress name fromoauth2-proxy
tooauth2-proxy-api
.charts/hub/templates/kerberos-hub/hub-frontend-demo.yaml
: Changed the ingress name fromoauth2-proxy
tooauth2-proxy-frontend-demo
.charts/hub/templates/kerberos-hub/hub-frontend.yaml
: Changed the ingress name fromoauth2-proxy
tooauth2-proxy-frontend
.Overall, these changes enhance the project's version management and improve the clarity and specificity of ingress resource naming, contributing to a more robust and maintainable codebase.