LFX Mentorship 2024_03 test task #6590
antoninbas
started this conversation in
General
Replies: 2 comments 9 replies
-
For submissions, please reply to this thread with the requested information |
Beta Was this translation helpful? Give feedback.
7 replies
-
@antoninbas Do we need to submit a proposal? |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
First, we'd like to thank everyone who is interested in taking part to the LFX Mentorship program with us, and we are excited to welcome new contributors to Project Antrea.
We only submitted one project for this iteration of the LFX Mentorship program:
In order to help us find the right candidate, we have prepared a simple task. It's a good opportunity for you to get familiar with Antrea, and for us to ensure that you have some of the required skills for a successful mentorship. We do not expect this task to take more than a couple of hours.
Remember to apply at https://lfx.linuxfoundation.org/tools/mentorship/ in addition to completing the task.
Task details
Steps:
run(o *Options)
function.klog.InfoS
(look at the rest of the source code for examples).klog.InfoS
is a "structured logging" primitive and lets you include key-value pairs with your log message. Your log message should include the following data: 1) your Github username, and 2) the name of the K8s Pod executing the program (antrea-agent and antrea-controller are meant to be run as Pods). Hint: You will need theenv.GetPodName()
function from theantrea.io/antrea/pkg/util/env
package.make
. Again you may find it useful to refer to CONTRIBUTING.md.kubectl
, dump the logs for each antrea Pod (1 controller Pod and 2 agent Pods) and copy the first 10 lines of each log to a local file at the root of the repository: (controller.txt
,agent1.txt
,agent2.txt
). Among the log lines should be the one you added in step 3.antrea-ovs
container of the antrea-agent Pod (any one of them) and find out the version of OVS which is installed, using the appropriate OVS command. Write it to to a local file (ovs-version.txt
) at the root of the repository. To get the OVS version, you will need to use theovs-vsctl
command-line utility (find the documentation online).antctl version
command and write the output toantrea-version.txt
, at the root of the repository.lfx-mentorship
Namespace.deployment.yml
, create a single-replica Deployment in thelfx-mentorship
Namespace, using theantrea/toolbox:1.4
container image.anp.yml
, create an AntreaNetworkPolicy
Custom Resource in thelfx-mentorship
Namespace. The policy must apply to all Pods in the Namespace. The policy must specify 3 egress rules, in this order: a) one rule toAllow
traffic to all Pods in all Namespaces (hint: usenamespaceSelector: {}
for this), b) one FQDN rule toAllow
traffic to theapi.github.com
domain, and c) one rule toReject
all remaining traffic (hint: omit theto
field to match all). You will need to refer to the Antrea documentation: https://github.com/antrea-io/antrea/blob/main/docs/antrea-network-policy.mdNetworkPolicy
using these 2 shell commands:curl -I api.github.com
,curl -I www.example.com
. It may take a few tries for you to write the correct policy. Once the 2curl
commands produce the desired output, take a screenshot of your terminal window and save it as a PNG, JPEG or PDF file to the root of the repository (e.g., asscreenshot.png
). The screenshot should show the outcome of bothcurl
commands..txt
files + the 2.yml
files + the screenshot) as a single commit. All the new files should be at the root of the repository. We ask that you:antrea-lfx-mentorship-2024_03-6229
.Submissions
Upon completing the task, reply to the thread below with the following information:
Make sure that your Github repository use the correct branch name, as specified above in the task description.
For any queries, please reply reply to this discussion below or post in the
#antrea
channel in the K8s Slack workspace. Do not send emails or DMs to ask for assistance, use public channels only. We are happy to provide some assistance if you get stuck or if some instructions are not clear enough.Deadlines
Task Deadline: Submissions must be completed by August 16, 5:00 PM PDT.
LFX Application Deadline: LFX applicants must submit by August 13, 5:00 PM PDT.
Beta Was this translation helpful? Give feedback.
All reactions