Skip to content
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 GatewayAPI resources to sysdump #1569

Merged
merged 1 commit into from
May 25, 2023

Conversation

meyskens
Copy link
Member

@meyskens meyskens commented May 3, 2023

This adds all GatewayAPI objects to the sysdump as well as the IngressClass object. This will be helpful for troubleshooting GatewayAPI related issues.
The objects are dumped into YAML if available prefixed with gatewayapi- for ease of use.

Fixes #1567

@meyskens meyskens requested review from a team as code owners May 3, 2023 11:25
@meyskens meyskens requested review from youngnick and squeed May 3, 2023 11:25
@meyskens meyskens temporarily deployed to ci May 3, 2023 11:25 — with GitHub Actions Inactive
@squeed
Copy link
Contributor

squeed commented May 3, 2023

Got a lint failure:

  Warning: unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _ (revive)
  Warning: unused-parameter: parameter 'ctx' seems to be unused, consider removing or renaming it as _ (revive)

@squeed
Copy link
Contributor

squeed commented May 3, 2023

Is there any chance that there is secret data that will need to be scrubbed? I dunno, I always think of Ingress and brethren as having scary annotations.

Copy link
Contributor

@squeed squeed left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good on fixing lint; see question about potential secrets (probably not an issue).

@youngnick
Copy link

No, we've specifically designed Gateway API to only use structured data, and to keep secret stuff in Secrets. I hate annotations for Ingress stuff too.

This adds all GatewayAPI objects to the sysdump as well as the
IngressClass object. This will be helpful for troubleshooting GatewayAPI
related issues.
The objects are dumped into YAML if available prefixed with gatewayapi-
for ease of use.

Signed-off-by: Maartje Eyskens <maartje.eyskens@isovalent.com>
@meyskens meyskens temporarily deployed to ci May 10, 2023 12:37 — with GitHub Actions Inactive
@tklauser tklauser merged commit 503413d into cilium:main May 25, 2023
14 of 15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Sysdump: improve experience for Gateway API + ingress
4 participants