`K3s`

Open
#99 16 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
kubernetes
Domain
devops

Research direction

Read the linked K3s documentation, then compare the context in issues #96 and #57. The issue defines no file, proposed change, or completion criteria, so work would first require agreement on whether comparative K3s and Kamal learning content is wanted.

Written by the indexing model from the issue text.

Description

discuss technical

While learning about Kamal #96 I cannot help but think it's similar to - but simpler than - K3s
https://docs.k3s.io -> https://github.com/k3s-io/k3s 🔗

So the question is: is it worth using K3s over Kamal? 🧑‍💻 🤷‍♂️

In my mind, the only reason to use K3s or K8s is to conform to expected norm. 🫤
Not saying they are bad, obviously not, just that in most cases they are overkill. 🔨 🥜

Related to: https://github.com/dwyl/learn-devops/issues/57

Dominant language
Shell
Stars
443
Forks
177
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dwyl/learn-devops

All issues in dwyl/learn-devops

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.