fix: add manifests to quickstart - #122
Open
oliverbaehler wants to merge 1 commit into
Open
Conversation
Signed-off-by: Oliver Baehler <oliver@sudo-i.net>
✅ Deploy Preview for docs-projectcapsule ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the extended quickstart documentation to add additional manifest examples and links, aiming to make it easier for readers to apply ready-made Capsule/Kubernetes resources during onboarding.
Changes:
- Adjusts the Permission Bindings example to use a tenant-templated operators group name.
- Adds new quickstart documentation sections for LimitRanges, NetworkPolicies, and a “Full Tenant” example, each with “Get Here” manifest links and inline YAML.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Comment on lines
206
to
+209
| - clusterRoleName: 'edit' | ||
| subjects: | ||
| - kind: Group | ||
| name: "solar:operators" | ||
| name: "tenant:{{ .tenant.metadata.name }}:operators" |
| service-level-gold 2026-07-24T10:00:00Z | ||
| ``` | ||
|
|
||
| ### Networkpolicies |
Comment on lines
+310
to
+312
| Distribute a [`NetworkPolicy`](https://kubernetes.io/docs/concepts/services-networking/network-policies/) to all `Namespaces` of a `Tenant` to enforce a certain network policy for all workloads within the `Tenant`/`Namespace`. The following `NetworkPolicy` is an attempt to achieve a default deny policy for all `Namespaces` of the `Tenant` but allow intra-namespace communication and allow communication between all `Namespaces` of the same `Tenant`. It also allows communication to system namespaces (eg. monitoring, ingress, etc.). [Read More](https://kubernetes.io/docs/concepts/security/multi-tenancy/#network-isolation) | ||
|
|
||
| [Get Here](/docs/quickstart/gtr-netpol.yaml) |
Comment on lines
+382
to
+385
| Here we have two `Tenants` with different rules and permissions. The `solar` tenant is a production tenant with multiple application stages with strict rules and permissions, while the `lunar` tenant is a development tenant with more relaxed rules and permissions. | ||
|
|
||
| [Get Here](/docs/quickstart/full-tenant.yaml) | ||
|
|
Comment on lines
+386
to
+388
| ```yaml | ||
| # solar.yaml | ||
| --- |
sandert-k8s
reviewed
Aug 12, 2026
| - clusterRoleName: 'view' | ||
| subjects: | ||
| - kind: Group | ||
| name: "solar:operators" |
Collaborator
There was a problem hiding this comment.
Suggested change
| name: "tenant:{{ .tenant.metadata.name }}:operators" |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.