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

Update dependency stakater/vale-package to v0.0.52 (main) #231

Merged
merged 3 commits into from
Feb 5, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .vale.ini
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
StylesPath = styles
MinAlertLevel = warning

Packages = https://github.com/stakater/vale-package/releases/download/v0.0.45/Stakater.zip
Packages = https://github.com/stakater/vale-package/releases/download/v0.0.52/Stakater.zip
Vocab = Stakater

# Only check MarkDown files
Expand Down
4 changes: 2 additions & 2 deletions content/about/key-features.md
Original file line number Diff line number Diff line change
Expand Up @@ -54,9 +54,9 @@ Provides tools to forecast and allocate resources effectively, ensuring optimal

## Integration Features

### HashiCorp Vault Multitenancy
### Hashicorp Vault Multitenancy

Multi Tenant Operator extends the tenants permission model to HashiCorp Vault where it can create Vault paths and greatly ease the overhead of managing RBAC in Vault. Tenant users can manage their own secrets without the concern of someone else having access to their Vault paths.
Multi Tenant Operator extends the tenants permission model to Hashicorp Vault where it can create Vault paths and greatly ease the overhead of managing RBAC in Vault. Tenant users can manage their own secrets without the concern of someone else having access to their Vault paths.

More details on [Vault Multitenancy](../how-to-guides/enabling-multi-tenancy-vault.md)

Expand Down
2 changes: 1 addition & 1 deletion content/explanation/multi-tenancy-vault.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

## Vault Multitenancy

HashiCorp Vault is an identity-based secret and encryption management system. Vault validates and authorizes a system's clients (users, machines, apps) before providing them access to secrets or stored sensitive data.
Hashicorp Vault is an identity-based secret and encryption management system. Vault validates and authorizes a system's clients (users, machines, apps) before providing them access to secrets or stored sensitive data.

## Vault integration in Multi Tenant Operator

Expand Down
2 changes: 1 addition & 1 deletion content/how-to-guides/integrating-vault.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ This guide provides step-by-step instructions for integrating **Vault** with **K

- Microsoft Entra ID configured for OIDC.
- Keycloak setup with an Identity Provider (IDP) pointing to Microsoft Entra ID.
- HashiCorp Vault installed and configured.
- Hashicorp Vault installed and configured.
- [Vault Configured in IntegrationConfig](enabling-multi-tenancy-vault.md)

## Steps to Implement Group-Based Access Control with Group IDs
Expand Down
2 changes: 1 addition & 1 deletion content/installation/kubernetes.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ This document contains instructions on installing, uninstalling and configuring

## Installing via Helm CLI

* Public Helm Chart of MTO is available at [Stakater GHCR Packages](https://github.com/orgs/stakater/packages/container/package/public/charts/multi-tenant-operator) and available Helm options can be seen at [MTO Helm Chart Options](./helm.md)
* Public Helm Chart of MTO is available at [Stakater ghcr Packages](https://github.com/orgs/stakater/packages/container/package/public/charts/multi-tenant-operator) and available Helm options can be seen at [MTO Helm Chart Options](./helm.md)

* Use `helm install` command to install MTO helm chart. Here, `bypassedGroups` has the names of groups which are designated as Cluster Admins in your cluster. For this example, we will use `system:masters`

Expand Down
Loading