-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Add Alluxio master web ports to Ingress in Helm chart #14290
base: master-2.x
Are you sure you want to change the base?
Conversation
{{- if .Capabilities.APIVersions.Has "networking.k8s.io/v1beta1" }} | ||
apiVersion: networking.k8s.io/v1beta1 | ||
{{- else }} | ||
apiVersion: networking.k8s.io/v1 | ||
{{- end }} |
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.
The networking.k8s.io/v1
API version were introduced in Kubernetes 1.19+, and the networking.k8s.io/v1beta1
API version is being deprecated as of 1.22.
I opted to make the else
case be the GA version of the API version rather than the beta one to indicate that use of the beta API version is an edge-case rather than the default.
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.
Wow this is finally coming! I anticipate a lot of compatibility issues raised and much tweaks like this have to be added in our helm chart :(
I never really realized how fast k8s versions change and how short their support window is for each version. I'll give it a bit more thoughts and probably add comments later.
Codecov Report
@@ Coverage Diff @@
## master #14290 +/- ##
=============================================
- Coverage 43.03% 30.31% -12.73%
+ Complexity 9308 5935 -3373
=============================================
Files 1448 1448
Lines 84203 84203
Branches 10178 10178
=============================================
- Hits 36239 25524 -10715
- Misses 44960 56555 +11595
+ Partials 3004 2124 -880
Continue to review full report at Codecov.
|
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.
Added some quick comments. I haven't really seen an real Ingress so I'll probably explore a bit more before adding more comments or giving PTAL. Thx!
service: | ||
name: {{ $fullName }}-{{ $masterName }} | ||
port: | ||
number: 19999 |
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.
Parameterize the port?
service: | ||
name: {{ $fullName }}-{{ $masterName }} | ||
port: | ||
number: 20002 |
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.
Same as above
{{- if .Capabilities.APIVersions.Has "networking.k8s.io/v1beta1" }} | ||
apiVersion: networking.k8s.io/v1beta1 | ||
{{- else }} | ||
apiVersion: networking.k8s.io/v1 | ||
{{- end }} |
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.
Wow this is finally coming! I anticipate a lot of compatibility issues raised and much tweaks like this have to be added in our helm chart :(
I never really realized how fast k8s versions change and how short their support window is for each version. I'll give it a bit more thoughts and probably add comments later.
This Ingress definition currently doesn't work because the relative links in our web pages target |
Test validation of this PR is blocked by this git issue. The ingress definition itself correctly reroutes the initial request, but subsequent links from the webpage are not being routed through the right base path. I was using the nginx ingress controller for testing.
Perhaps the X-Forwarded-For header could be used? |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in two weeks if no further activity occurs. Thank you for your contributions. |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in two weeks if no further activity occurs. Thank you for your contributions. |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in two weeks if no further activity occurs. Thank you for your contributions. |
This PR just introduces a very simplified Ingress to expose the Master pod(s)
web
andjob-web
ports.Note that the Helm chart is not responsible for defining corresponding Ingress Controllers, so this is just a utility for defining an
Ingress
for the Master web ports.