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

k8s/slim: Clarify instructions for updating slim files #29877

Merged
merged 1 commit into from Jan 9, 2024
Merged

k8s/slim: Clarify instructions for updating slim files #29877

merged 1 commit into from Jan 9, 2024

Conversation

christarazi
Copy link
Member

Signed-off-by: Chris Tarazi chris@isovalent.com

@christarazi christarazi requested a review from a team as a code owner December 13, 2023 23:46
@christarazi christarazi added kind/enhancement This would improve or streamline existing functionality. sig/k8s Impacts the kubernetes API, or kubernetes -> cilium internals translation layers. labels Dec 13, 2023
@christarazi christarazi added release-note/misc This PR makes changes that have no direct user impact. area/documentation Impacts the documentation, including textual changes, sphinx, or other doc generation code. labels Dec 13, 2023
@christarazi
Copy link
Member Author

/test

aanm
aanm reviewed Dec 14, 2023
View reviewed changes
pkg/k8s/slim/README.md Outdated Show resolved Hide resolved
@christarazi
Copy link
Member Author

christarazi commented Dec 14, 2023 •
edited

/test

Edit:

@christarazi
k8s/slim: Clarify instructions for updating slim files
07dd56d 
Signed-off-by: Chris Tarazi <chris@isovalent.com>
@christarazi christarazi force-pushed the pr/christarazi/update-k8s-docs branch from 81f6db4 to 07dd56d Compare January 9, 2024 00:52
@christarazi
Copy link
Member Author

christarazi commented Jan 9, 2024 •
edited

/test

Edit:

@christarazi christarazi added the needs-backport/1.15 This PR / issue needs backporting to the v1.15 branch label Jan 9, 2024
@maintainer-s-little-helper maintainer-s-little-helper bot added this to Needs backport from main in v1.15.0-rc.1 Jan 9, 2024
@christarazi christarazi added this pull request to the merge queue Jan 9, 2024
@maintainer-s-little-helper maintainer-s-little-helper bot added the ready-to-merge This PR has passed all tests and received consensus from code owners to merge. label Jan 9, 2024
Merged via the queue into cilium:main with commit cddb591 Jan 9, 2024
62 checks passed
@christarazi christarazi deleted the pr/christarazi/update-k8s-docs branch January 9, 2024 19:31
@jibi jibi mentioned this pull request Jan 12, 2024
Merged
32 tasks
@jibi jibi added backport-pending/1.15 The backport for Cilium 1.15.x for this PR is in progress. and removed needs-backport/1.15 This PR / issue needs backporting to the v1.15 branch labels Jan 12, 2024
@aanm aanm mentioned this pull request Jan 16, 2024
Merged
@giorio94 giorio94 added backport-done/1.15 The backport for Cilium 1.15.x for this PR is done. and removed backport-pending/1.15 The backport for Cilium 1.15.x for this PR is in progress. labels Jan 29, 2024
@maintainer-s-little-helper maintainer-s-little-helper bot moved this from Needs backport from main to Backport done to v1.15 in v1.15.0-rc.1 Jan 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@aanm aanm aanm left review comments

@joamaki joamaki joamaki approved these changes

Assignees
No one assigned
Labels
area/documentation Impacts the documentation, including textual changes, sphinx, or other doc generation code. backport-done/1.15 The backport for Cilium 1.15.x for this PR is done. kind/enhancement This would improve or streamline existing functionality. ready-to-merge This PR has passed all tests and received consensus from code owners to merge. release-note/misc This PR makes changes that have no direct user impact. sig/k8s Impacts the kubernetes API, or kubernetes -> cilium internals translation layers.
Projects
No open projects
v1.15.0-rc.1
Backport done to v1.15
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
5 participants
@christarazi @joamaki @aanm @jibi @giorio94