Skip to content

Commit

Permalink
Update charts
Browse files Browse the repository at this point in the history
/skip-trigger

Signed-off-by: 1gtm <[email protected]>
  • Loading branch information
1gtm committed Oct 16, 2023
1 parent b0537dc commit 302c3e3
Show file tree
Hide file tree
Showing 2,479 changed files with 133,090 additions and 562 deletions.
67 changes: 67 additions & 0 deletions charts/accessanalyzerawsupboundio-analyzer-editor/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,67 @@
# Analyzer Editor

[Analyzer Editor by AppsCode](https://byte.builders) - Analyzer Editor

## TL;DR;

```bash
$ helm repo add bytebuilders-ui https://bundles.byte.builders/ui/
$ helm repo update
$ helm search repo bytebuilders-ui/accessanalyzerawsupboundio-analyzer-editor --version=v0.4.18
$ helm upgrade -i accessanalyzerawsupboundio-analyzer-editor bytebuilders-ui/accessanalyzerawsupboundio-analyzer-editor -n default --create-namespace --version=v0.4.18
```

## Introduction

This chart deploys a Analyzer Editor on a [Kubernetes](http://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.

## Prerequisites

- Kubernetes 1.20+

## Installing the Chart

To install/upgrade the chart with the release name `accessanalyzerawsupboundio-analyzer-editor`:

```bash
$ helm upgrade -i accessanalyzerawsupboundio-analyzer-editor bytebuilders-ui/accessanalyzerawsupboundio-analyzer-editor -n default --create-namespace --version=v0.4.18
```

The command deploys a Analyzer Editor on the Kubernetes cluster in the default configuration. The [configuration](#configuration) section lists the parameters that can be configured during installation.

> **Tip**: List all releases using `helm list`
## Uninstalling the Chart

To uninstall the `accessanalyzerawsupboundio-analyzer-editor`:

```bash
$ helm uninstall accessanalyzerawsupboundio-analyzer-editor -n default
```

The command removes all the Kubernetes components associated with the chart and deletes the release.

## Configuration

The following table lists the configurable parameters of the `accessanalyzerawsupboundio-analyzer-editor` chart and their default values.

| Parameter | Description | Default |
|--------------------|-------------|----------------------------------------------------|
| apiVersion | | <code>accessanalyzer.aws.upbound.io/v1beta1</code> |
| kind | | <code>Analyzer</code> |
| metadata.name | | <code>analyzer</code> |
| metadata.namespace | | <code>""</code> |


Specify each parameter using the `--set key=value[,key=value]` argument to `helm upgrade -i`. For example:

```bash
$ helm upgrade -i accessanalyzerawsupboundio-analyzer-editor bytebuilders-ui/accessanalyzerawsupboundio-analyzer-editor -n default --create-namespace --version=v0.4.18 --set apiVersion=accessanalyzer.aws.upbound.io/v1beta1
```

Alternatively, a YAML file that specifies the values for the parameters can be provided while
installing the chart. For example:

```bash
$ helm upgrade -i accessanalyzerawsupboundio-analyzer-editor bytebuilders-ui/accessanalyzerawsupboundio-analyzer-editor -n default --create-namespace --version=v0.4.18 --values values.yaml
```
67 changes: 67 additions & 0 deletions charts/accessanalyzerawsupboundio-archiverule-editor/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,67 @@
# ArchiveRule Editor

[ArchiveRule Editor by AppsCode](https://byte.builders) - ArchiveRule Editor

## TL;DR;

```bash
$ helm repo add bytebuilders-ui https://bundles.byte.builders/ui/
$ helm repo update
$ helm search repo bytebuilders-ui/accessanalyzerawsupboundio-archiverule-editor --version=v0.4.18
$ helm upgrade -i accessanalyzerawsupboundio-archiverule-editor bytebuilders-ui/accessanalyzerawsupboundio-archiverule-editor -n default --create-namespace --version=v0.4.18
```

## Introduction

This chart deploys a ArchiveRule Editor on a [Kubernetes](http://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.

## Prerequisites

- Kubernetes 1.20+

## Installing the Chart

To install/upgrade the chart with the release name `accessanalyzerawsupboundio-archiverule-editor`:

```bash
$ helm upgrade -i accessanalyzerawsupboundio-archiverule-editor bytebuilders-ui/accessanalyzerawsupboundio-archiverule-editor -n default --create-namespace --version=v0.4.18
```

The command deploys a ArchiveRule Editor on the Kubernetes cluster in the default configuration. The [configuration](#configuration) section lists the parameters that can be configured during installation.

> **Tip**: List all releases using `helm list`
## Uninstalling the Chart

To uninstall the `accessanalyzerawsupboundio-archiverule-editor`:

```bash
$ helm uninstall accessanalyzerawsupboundio-archiverule-editor -n default
```

The command removes all the Kubernetes components associated with the chart and deletes the release.

## Configuration

The following table lists the configurable parameters of the `accessanalyzerawsupboundio-archiverule-editor` chart and their default values.

| Parameter | Description | Default |
|--------------------|-------------|----------------------------------------------------|
| apiVersion | | <code>accessanalyzer.aws.upbound.io/v1beta1</code> |
| kind | | <code>ArchiveRule</code> |
| metadata.name | | <code>archiverule</code> |
| metadata.namespace | | <code>""</code> |


Specify each parameter using the `--set key=value[,key=value]` argument to `helm upgrade -i`. For example:

```bash
$ helm upgrade -i accessanalyzerawsupboundio-archiverule-editor bytebuilders-ui/accessanalyzerawsupboundio-archiverule-editor -n default --create-namespace --version=v0.4.18 --set apiVersion=accessanalyzer.aws.upbound.io/v1beta1
```

Alternatively, a YAML file that specifies the values for the parameters can be provided while
installing the chart. For example:

```bash
$ helm upgrade -i accessanalyzerawsupboundio-archiverule-editor bytebuilders-ui/accessanalyzerawsupboundio-archiverule-editor -n default --create-namespace --version=v0.4.18 --values values.yaml
```
Original file line number Diff line number Diff line change
@@ -0,0 +1,67 @@
# AccessLevel Editor

[AccessLevel Editor by AppsCode](https://byte.builders) - AccessLevel Editor

## TL;DR;

```bash
$ helm repo add bytebuilders-ui https://bundles.byte.builders/ui/
$ helm repo update
$ helm search repo bytebuilders-ui/accesscontextmanagergcpupboundio-accesslevel-editor --version=v0.4.18
$ helm upgrade -i accesscontextmanagergcpupboundio-accesslevel-editor bytebuilders-ui/accesscontextmanagergcpupboundio-accesslevel-editor -n default --create-namespace --version=v0.4.18
```

## Introduction

This chart deploys a AccessLevel Editor on a [Kubernetes](http://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.

## Prerequisites

- Kubernetes 1.20+

## Installing the Chart

To install/upgrade the chart with the release name `accesscontextmanagergcpupboundio-accesslevel-editor`:

```bash
$ helm upgrade -i accesscontextmanagergcpupboundio-accesslevel-editor bytebuilders-ui/accesscontextmanagergcpupboundio-accesslevel-editor -n default --create-namespace --version=v0.4.18
```

The command deploys a AccessLevel Editor on the Kubernetes cluster in the default configuration. The [configuration](#configuration) section lists the parameters that can be configured during installation.

> **Tip**: List all releases using `helm list`
## Uninstalling the Chart

To uninstall the `accesscontextmanagergcpupboundio-accesslevel-editor`:

```bash
$ helm uninstall accesscontextmanagergcpupboundio-accesslevel-editor -n default
```

The command removes all the Kubernetes components associated with the chart and deletes the release.

## Configuration

The following table lists the configurable parameters of the `accesscontextmanagergcpupboundio-accesslevel-editor` chart and their default values.

| Parameter | Description | Default |
|--------------------|-------------|----------------------------------------------------------|
| apiVersion | | <code>accesscontextmanager.gcp.upbound.io/v1beta1</code> |
| kind | | <code>AccessLevel</code> |
| metadata.name | | <code>accesslevel</code> |
| metadata.namespace | | <code>""</code> |


Specify each parameter using the `--set key=value[,key=value]` argument to `helm upgrade -i`. For example:

```bash
$ helm upgrade -i accesscontextmanagergcpupboundio-accesslevel-editor bytebuilders-ui/accesscontextmanagergcpupboundio-accesslevel-editor -n default --create-namespace --version=v0.4.18 --set apiVersion=accesscontextmanager.gcp.upbound.io/v1beta1
```

Alternatively, a YAML file that specifies the values for the parameters can be provided while
installing the chart. For example:

```bash
$ helm upgrade -i accesscontextmanagergcpupboundio-accesslevel-editor bytebuilders-ui/accesscontextmanagergcpupboundio-accesslevel-editor -n default --create-namespace --version=v0.4.18 --values values.yaml
```
Original file line number Diff line number Diff line change
@@ -0,0 +1,67 @@
# AccessLevelCondition Editor

[AccessLevelCondition Editor by AppsCode](https://byte.builders) - AccessLevelCondition Editor

## TL;DR;

```bash
$ helm repo add bytebuilders-ui https://bundles.byte.builders/ui/
$ helm repo update
$ helm search repo bytebuilders-ui/accesscontextmanagergcpupboundio-accesslevelcondition-editor --version=v0.4.18
$ helm upgrade -i accesscontextmanagergcpupboundio-accesslevelcondition-editor bytebuilders-ui/accesscontextmanagergcpupboundio-accesslevelcondition-editor -n default --create-namespace --version=v0.4.18
```

## Introduction

This chart deploys a AccessLevelCondition Editor on a [Kubernetes](http://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.

## Prerequisites

- Kubernetes 1.20+

## Installing the Chart

To install/upgrade the chart with the release name `accesscontextmanagergcpupboundio-accesslevelcondition-editor`:

```bash
$ helm upgrade -i accesscontextmanagergcpupboundio-accesslevelcondition-editor bytebuilders-ui/accesscontextmanagergcpupboundio-accesslevelcondition-editor -n default --create-namespace --version=v0.4.18
```

The command deploys a AccessLevelCondition Editor on the Kubernetes cluster in the default configuration. The [configuration](#configuration) section lists the parameters that can be configured during installation.

> **Tip**: List all releases using `helm list`
## Uninstalling the Chart

To uninstall the `accesscontextmanagergcpupboundio-accesslevelcondition-editor`:

```bash
$ helm uninstall accesscontextmanagergcpupboundio-accesslevelcondition-editor -n default
```

The command removes all the Kubernetes components associated with the chart and deletes the release.

## Configuration

The following table lists the configurable parameters of the `accesscontextmanagergcpupboundio-accesslevelcondition-editor` chart and their default values.

| Parameter | Description | Default |
|--------------------|-------------|----------------------------------------------------------|
| apiVersion | | <code>accesscontextmanager.gcp.upbound.io/v1beta1</code> |
| kind | | <code>AccessLevelCondition</code> |
| metadata.name | | <code>accesslevelcondition</code> |
| metadata.namespace | | <code>""</code> |


Specify each parameter using the `--set key=value[,key=value]` argument to `helm upgrade -i`. For example:

```bash
$ helm upgrade -i accesscontextmanagergcpupboundio-accesslevelcondition-editor bytebuilders-ui/accesscontextmanagergcpupboundio-accesslevelcondition-editor -n default --create-namespace --version=v0.4.18 --set apiVersion=accesscontextmanager.gcp.upbound.io/v1beta1
```

Alternatively, a YAML file that specifies the values for the parameters can be provided while
installing the chart. For example:

```bash
$ helm upgrade -i accesscontextmanagergcpupboundio-accesslevelcondition-editor bytebuilders-ui/accesscontextmanagergcpupboundio-accesslevelcondition-editor -n default --create-namespace --version=v0.4.18 --values values.yaml
```
Original file line number Diff line number Diff line change
@@ -0,0 +1,67 @@
# AccessPolicy Editor

[AccessPolicy Editor by AppsCode](https://byte.builders) - AccessPolicy Editor

## TL;DR;

```bash
$ helm repo add bytebuilders-ui https://bundles.byte.builders/ui/
$ helm repo update
$ helm search repo bytebuilders-ui/accesscontextmanagergcpupboundio-accesspolicy-editor --version=v0.4.18
$ helm upgrade -i accesscontextmanagergcpupboundio-accesspolicy-editor bytebuilders-ui/accesscontextmanagergcpupboundio-accesspolicy-editor -n default --create-namespace --version=v0.4.18
```

## Introduction

This chart deploys a AccessPolicy Editor on a [Kubernetes](http://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.

## Prerequisites

- Kubernetes 1.20+

## Installing the Chart

To install/upgrade the chart with the release name `accesscontextmanagergcpupboundio-accesspolicy-editor`:

```bash
$ helm upgrade -i accesscontextmanagergcpupboundio-accesspolicy-editor bytebuilders-ui/accesscontextmanagergcpupboundio-accesspolicy-editor -n default --create-namespace --version=v0.4.18
```

The command deploys a AccessPolicy Editor on the Kubernetes cluster in the default configuration. The [configuration](#configuration) section lists the parameters that can be configured during installation.

> **Tip**: List all releases using `helm list`
## Uninstalling the Chart

To uninstall the `accesscontextmanagergcpupboundio-accesspolicy-editor`:

```bash
$ helm uninstall accesscontextmanagergcpupboundio-accesspolicy-editor -n default
```

The command removes all the Kubernetes components associated with the chart and deletes the release.

## Configuration

The following table lists the configurable parameters of the `accesscontextmanagergcpupboundio-accesspolicy-editor` chart and their default values.

| Parameter | Description | Default |
|--------------------|-------------|----------------------------------------------------------|
| apiVersion | | <code>accesscontextmanager.gcp.upbound.io/v1beta1</code> |
| kind | | <code>AccessPolicy</code> |
| metadata.name | | <code>accesspolicy</code> |
| metadata.namespace | | <code>""</code> |


Specify each parameter using the `--set key=value[,key=value]` argument to `helm upgrade -i`. For example:

```bash
$ helm upgrade -i accesscontextmanagergcpupboundio-accesspolicy-editor bytebuilders-ui/accesscontextmanagergcpupboundio-accesspolicy-editor -n default --create-namespace --version=v0.4.18 --set apiVersion=accesscontextmanager.gcp.upbound.io/v1beta1
```

Alternatively, a YAML file that specifies the values for the parameters can be provided while
installing the chart. For example:

```bash
$ helm upgrade -i accesscontextmanagergcpupboundio-accesspolicy-editor bytebuilders-ui/accesscontextmanagergcpupboundio-accesspolicy-editor -n default --create-namespace --version=v0.4.18 --values values.yaml
```
Loading

0 comments on commit 302c3e3

Please sign in to comment.