kubero-dev / kubero-dev/kubero

[FEATURE]: Digital Ocean or Linode Managed Kubernetes Node Autoscaling

Open
#381 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Idea/discussion
Dominant language
TypeScript
Stars
4.4k
Forks
212
PR merge metrics
No merged PRs in 30d

Description

Description

I wanted to know if i used digital ocean managed kubernetes service, with kubero then it autoscaling of nodes work well

Benefit i will get:

Possible solution

kubero and digital ocean managed kubernetes

Alternatives

porter.run

Additional information

No response

Contributor guide

Open the contributing guide

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.

Research direction

Start by reading the linked DigitalOcean and Linode Kubernetes autoscaling documentation and comparing their requirements with Kubero's current Kubernetes deployment behavior. Define the supported provider scope and verify that node autoscaling works reliably for the described GitHub deployment, UI, SSL, and Ingress workflow.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes
Domain
cloud, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.