docs: Add Makefile and documentation for "fast" development targets #27931
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
aanm
added
release-note/misc
aanm
force-pushed
the
pr/add-fast-targets
branch
from
5ccf15d
to
6a357ee
Compare
nebril
approved these changes
Sep 5, 2023
qmonnet
approved these changes
Sep 5, 2023
|
Is it something we could backport, so we could use it when troubleshooting issues on the older branches, as well? |
qmonnet
reviewed
Sep 5, 2023
This commit introduces documentation for "fast" development targets in Cilium. The "fast" targets allow for quicker development workflows by building Cilium locally and deploying it on an existing kind cluster. This approach eliminates the need to create and deploy Docker images each time a source code change is made. Additionally, the documentation has been updated to include these new Makefile targets and provides a quick start guide with essential information for working with Cilium. When a cluster is already running with a Cilium container, we can simply volume mount the binaries into the container and restart the pod to pick up the changes. A similar approach can be used for C code, with the caveat that the bpf/lib directory needs write permissions by Cilium to generate the C Header features file, making it impossible to use the volume as read-only. Since all nodes share the same kernel features, there won't be any conflicts when multiple nodes write to the same volume mount. Signed-off-by: André Martins <andre@cilium.io>
aanm
force-pushed
the
pr/add-fast-targets
branch
from
6a357ee
to
873ba97
Compare
|
/test |
|
Very cool! Do you think that at some point we could combine the |
jibi
added
the
needs-backport/1.14
gandro
added
backport-pending/1.14
gandro
added
backport-done/1.14
sayboras
added a commit
to sayboras/cilium
that referenced
this pull request
Feb 1, 2024
This is to print out command hints for Linux host, so that new Cilium contributors didn't need to check docs. Relates: cilium#27931 Signed-off-by: Tam Mach <tam.mach@cilium.io>
github-merge-queue bot
pushed a commit
that referenced
this pull request
Feb 1, 2024
This is to print out command hints for Linux host, so that new Cilium contributors didn't need to check docs. Relates: #27931 Signed-off-by: Tam Mach <tam.mach@cilium.io>
Pionerd
pushed a commit
to Pionerd/cilium
that referenced
this pull request
Feb 13, 2024
This is to print out command hints for Linux host, so that new Cilium contributors didn't need to check docs. Relates: cilium#27931 Signed-off-by: Tam Mach <tam.mach@cilium.io>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit introduces documentation for "fast" development targets in Cilium. The "fast" targets allow for quicker development workflows by building Cilium locally and deploying it on an existing kind cluster. This approach eliminates the need to create and deploy Docker images each time a source code change is made.
Additionally, the documentation has been updated to include these new Makefile targets and provides a quick start guide with essential information for working with Cilium.
When a cluster is already running with a Cilium container, we can simply volume mount the binaries into the container and restart the pod to pick up the changes. A similar approach can be used for C code, with the caveat that the bpf/lib directory needs write permissions by Cilium to generate the C Header features file, making it impossible to use the volume as read-only. Since all nodes share the same kernel features, there won't be any conflicts when multiple nodes write to the same volume mount.