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.

Sign up for GitHub

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

Jump to bottom

[cluster-local-domain-tls] use informers instead of kubeclient #14797

Open
ReToCode opened this issue Jan 16, 2024 · 1 comment
Open

[cluster-local-domain-tls] use informers instead of kubeclient #14797

ReToCode opened this issue Jan 16, 2024 · 1 comment
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@ReToCode
Copy link
Member

ReToCode commented Jan 16, 2024 •
edited
Loading

Use informers instead of kubeclient:
@ReToCode ReToCode changed the title Serving improvement: Use informers instead of kubeclient [cluster-local-domain-tls] use informers instead of kubeclient Jan 16, 2024
@ReToCode ReToCode mentioned this issue Jan 16, 2024
Merged
@github-actions GitHub Actions
Copy link

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 16, 2024
@ReToCode ReToCode added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Apr 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
Serving Encryption
Status: No status
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ReToCode