Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Getting Started and Other Docs #527

Merged
merged 24 commits into from
Jul 23, 2021
Merged

Getting Started and Other Docs #527

merged 24 commits into from
Jul 23, 2021

Conversation

geoffcline
Copy link
Contributor

@geoffcline geoffcline commented Jul 22, 2021

Issue, if available: N/A

Description of changes:

paths to review:

website/content/en/docs/getting-started/_index.md

do not review paths:

docs/*

I respectfully submit that housing the HTML here makes PRs very confusing. Additionally, this code only works on local previews, not GH pages.

Screenshots
karpenter docs

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@geoffcline geoffcline changed the title Preview web [WIP] getting started and other docs Jul 22, 2021
@akestner
Copy link
Contributor

To get ahead of potential rabbit holes, I'm working on the hosting side of things now and will surface a PR with a recommendation

Copy link
Contributor

@njtran njtran left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice work! Just a couple of nits and possible suggestions.

docs/404.html Outdated
@@ -3,36 +3,36 @@
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
<meta name="generator" content="Hugo 0.85.0" /><META NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW">
<meta name="generator" content="Hugo 0.84.1" /><META NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW">
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this referring to a version of Hugo? Is there a reason we wouldn't want to use the most recent version (seems like 0.86.0

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is mooted by #528 build on netlify

docs/docs/getting-started/eks-config.yaml Outdated Show resolved Hide resolved
website/content/en/docs/dev-guide.md Outdated Show resolved Hide resolved
website/content/en/docs/faq.md Outdated Show resolved Hide resolved
website/content/en/docs/getting-started/_index.md Outdated Show resolved Hide resolved
Use helm to deploy Karpenter to the cluster.

We created a Kubernetes service account when we created the cluster using
eksctl. Thus, we don't need the helm chart to do that.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great. WDYT about having a command here (or a link to a command) to patch the serviceAccount for BYOC experiences or debugging purposes?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i agree but i think that's out of scope for the PR right now.

website/content/en/docs/getting-started/_index.md Outdated Show resolved Hide resolved

### Create Workload

This deployment uses the [pause image](https://www.ianlewis.org/en/almighty-pause-container) and starts with zero replicas.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We also have the feature to include a karpenter.sh/do-not-evict:true annotation for pods they don't want to evict. This is a pretty specific feature, so it may overcomplicate this guide. WDYT?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i'll include that in the annotations section

website/content/en/docs/getting-started/_index.md Outdated Show resolved Hide resolved
website/content/en/docs/getting-started/eks-config.yaml Outdated Show resolved Hide resolved
Copy link
Contributor

@akestner akestner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great work! I think this is definitely on the right track and a huge improvement over the current in-repo docs. Let's keep pushing on these to get them completed and hopefully we can get this published before the Bug Bash tomorrow.

website/content/en/docs/_index.md Show resolved Hide resolved
website/content/en/docs/dev-guide.md Outdated Show resolved Hide resolved
website/content/en/docs/dev-guide.md Outdated Show resolved Hide resolved
website/content/en/docs/dev-guide.md Outdated Show resolved Hide resolved
website/content/en/docs/faq.md Outdated Show resolved Hide resolved
Yes. The Kubernetes Eviction API will not delete pods that violate a [Pod Disruption Budget (PDB)](https://kubernetes.io/docs/tasks/run-application/configure-pdb/). It also disallows eviction of any pod covered by multiple PDBs, so most users will want to avoid overlapping selectors. See [this](https://kubernetes.io/docs/concepts/workloads/pods/disruptions/#pod-disruption-budgets) for more.
### Does Karpenter support scale to zero?
Yes. Provisioners start at zero and launch or terminate nodes as necessary. We recommend that customers maintain a small amount of static capacity to bootstrap system controllers or run Karpenter outside of their cluster.
## Compatibility
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's bump this section up since these are more common questions than some of the more prominently placed ones.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

moved ### Does Karpenter support scale to zero? to under ## General

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was referring to the ## Compatibility section, not scale to zero

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah ty

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

moved compatibility to the section after general.

website/content/en/docs/faq.md Outdated Show resolved Hide resolved
website/content/en/search.md Outdated Show resolved Hide resolved
website/package-lock.json Show resolved Hide resolved
@@ -0,0 +1,128 @@
<!doctype html>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should consider removing the build generated files under public/ as well as those built under ../docs/ since they cause a ton of noise in these PRs. Thoughts?

Even if we decide to keep these built files in the PR, there's no reason we'd need to have both these in public/ and those in ../docs/

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i have removed website/public

we will remove ../docs/ in the netlify pr (or a follow up)

@akestner akestner changed the title [WIP] getting started and other docs [WIP] Getting Started and Other Docs Jul 22, 2021
@geoffcline geoffcline force-pushed the preview-web branch 2 times, most recently from 2c2ee65 to ef45aa4 Compare July 23, 2021 02:49
@geoffcline geoffcline marked this pull request as ready for review July 23, 2021 02:50
@geoffcline geoffcline changed the title [WIP] Getting Started and Other Docs Getting Started and Other Docs Jul 23, 2021
@akestner
Copy link
Contributor

Hey @geoffcline, it looks like you've force pushed to this branch a few times since it was reviewed. Is there something that you're having trouble with?

Force pushing to branches that have been shared publicly is generally frowned upon because it rewrites the git repo's history, making it difficult to understand what changes have been made and when. Back in the day, I kept this printed out next to my desk for when I got into sticky situations.

Let me know if I can help, we can touch base tomorrow as needed.

@geoffcline
Copy link
Contributor Author

I was doing further development and forgot that those changes were showing up here.

Kubernetes website instructs users to force push with each new commit on a PR (they want 1 commit for each PR), so it's a bit of a learning curve for a different project.

@akestner
Copy link
Contributor

Ahh I see, glad to hear all's well. We're getting close here, giving this another look now

Copy link
Contributor

@akestner akestner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we're really close, couple minor suggestions and I think we'll be good to go!

website/content/en/docs/_index.md Show resolved Hide resolved
website/content/en/docs/provisioner-crd.md Outdated Show resolved Hide resolved
@akestner akestner self-requested a review July 23, 2021 17:51
@akestner
Copy link
Contributor

Ship it!

@geoffcline geoffcline merged commit 05abd58 into aws:main Jul 23, 2021
gfcroft pushed a commit to gfcroft/karpenter-provider-aws that referenced this pull request Nov 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants