Setting resource quotas such as cpu and memory limits/requests is easier said than done.

But why do you need this in the first place?

hello everyone, okay, so i did something recently with github action, rewrote and optimized a workflow of 900+ lines back to 200+

Hii 👋, i am sure you want peace of mind too, haha

Well, there is no way we would be discussing container supply chain security without talking about signing of container images.

You probably handling your manifest and deployment secrets in kube like this

apiVersion: apps/v1
kind: Deployment
metadata:
  creationTimestamp: null
  labels:
    app: hashicorp-vault-k8s
  name: hashicorp-vault-k8s
spec:
  replicas: 1
  selector:
    matchLabels:
      app: hashicorp-vault-k8s
  template:
    metadata:
      creationTimestamp: null
      labels:
        app: hashicorp-vault-k8s
    spec:
      containers:
      - image: busybox
        name:
        env:
        - name: API_KEY
          value: jduhdshieioieiisbbjsb
        - name: AWS_KEY
          value: 96859988gddjjdjds
        - name: WEBHOOK_SECRET
          value: jimjimjimokaynice

Yeah, being doing the CI/CD implementations via github workflow lately and i am also trapped in the process of making commits to trigger the workflows or better still making empty commits, haha.

Almost everyone knows how to use .gitignore, the git file that helps in keeping sensitive files like .env out of the tracking, commit and pushing process and also unwanted folders like node_modules and all.

But do you know secrets, hardcoded credentials and API aren't easy to deal with using .gitignore file? you dont want to keep your config.js or config.go file out of the commit process, this are essential files to your project.

For someone who just started writing Go, i have no idea about //go:embed feature which came with the released version: 1.16.

A project i was working on recently led to the discoveries.

Documentation is a vital part of any open source project or software.

It is the entry point or a fall back option for users of any open source project or software to read usage, installation instructions, to fix issues and learn more about the project.

Before we start, i will like to say, All these programs listed are not mandatory for you to contribute to open source.

But you can contribute to open source even if you don't get selected for these program, you can always contribute to open source programs anytime you want.

We try, next year we go again. ✌🏽✌🏽 E go be.