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 upstream specifications to their latest version #203

Merged
merged 1 commit into from
Oct 4, 2024
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
Original file line number Diff line number Diff line change
Expand Up @@ -60,5 +60,6 @@ Required:
Optional:

- `hook_images_url_path` (String) HookImagesURLPath can be used to override the default Hook images path to pull from a local server.
- `load_balancer_interface` (String) LoadBalancerInterface can be used to configure a load balancer interface for the Tinkerbell stack.
- `os_image_url` (String) OSImageURL can be used to override the default OS image path to pull from a local server. OSImageURL is a URL to the OS image used during provisioning. To perform modular upgrades the OSImageURL must be specified on the TinkerbellMachineConfig objects. You cannot specify an OSImageURL on the TinkerbellDatacenterConfig and TinkerbellMachineConfigs simultaneously. It must include the Kubernetes version(s). For example, a URL used for Kubernetes 1.27 could be http://localhost:8080/ubuntu-2204-1.27.tgz
- `skip_load_balancer_deployment` (Boolean) SkipLoadBalancerDeployment when set to 'true' can be used to skip deploying a load balancer to expose Tinkerbell stack. Users will need to deploy and configure a load balancer manually after the cluster is created.
60 changes: 48 additions & 12 deletions docs/data-sources/argoproj_io_argo_cd_v1alpha1_manifest.md
Original file line number Diff line number Diff line change
Expand Up @@ -260,16 +260,25 @@ Optional:

Required:

- `termination` (String) termination indicates termination type.
- `termination` (String) termination indicates termination type. * edge - TLS termination is done by the router and http is used to communicate with the backend (default) * passthrough - Traffic is sent straight to the destination without the router providing TLS termination * reencrypt - TLS termination is done by the router and https is used to communicate with the backend Note: passthrough termination is incompatible with httpHeader actions

Optional:

- `ca_certificate` (String) caCertificate provides the cert authority certificate contents
- `certificate` (String) certificate provides certificate contents
- `certificate` (String) certificate provides certificate contents. This should be a single serving certificate, not a certificate chain. Do not include a CA certificate.
- `destination_ca_certificate` (String) destinationCACertificate provides the contents of the ca certificate of the final destination. When using reencrypt termination this file should be provided in order to have routers use it for health checks on the secure connection. If this field is not specified, the router may provide its own destination CA and perform hostname validation using the short service name (service.namespace.svc), which allows infrastructure generated certificates to automatically verify.
- `insecure_edge_termination_policy` (String) insecureEdgeTerminationPolicy indicates the desired behavior for insecure connections to a route. While each router may make its own decisions on which ports to expose, this is normally port 80. * Allow - traffic is sent to the server on the insecure port (default) * Disable - no traffic is allowed on the insecure port. * Redirect - clients are redirected to the secure port.
- `external_certificate` (Attributes) externalCertificate provides certificate contents as a secret reference. This should be a single serving certificate, not a certificate chain. Do not include a CA certificate. The secret referenced should be present in the same namespace as that of the Route. Forbidden when 'certificate' is set. (see [below for nested schema](#nestedatt--spec--application_set--webhook_server--route--tls--external_certificate))
- `insecure_edge_termination_policy` (String) insecureEdgeTerminationPolicy indicates the desired behavior for insecure connections to a route. While each router may make its own decisions on which ports to expose, this is normally port 80. * Allow - traffic is sent to the server on the insecure port (edge/reencrypt terminations only) (default). * None - no traffic is allowed on the insecure port. * Redirect - clients are redirected to the secure port.
- `key` (String) key provides key file contents

<a id="nestedatt--spec--application_set--webhook_server--route--tls--external_certificate"></a>
### Nested Schema for `spec.application_set.webhook_server.route.tls.external_certificate`

Optional:

- `name` (String) name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names





Expand Down Expand Up @@ -526,16 +535,25 @@ Optional:

Required:

- `termination` (String) termination indicates termination type.
- `termination` (String) termination indicates termination type. * edge - TLS termination is done by the router and http is used to communicate with the backend (default) * passthrough - Traffic is sent straight to the destination without the router providing TLS termination * reencrypt - TLS termination is done by the router and https is used to communicate with the backend Note: passthrough termination is incompatible with httpHeader actions

Optional:

- `ca_certificate` (String) caCertificate provides the cert authority certificate contents
- `certificate` (String) certificate provides certificate contents
- `certificate` (String) certificate provides certificate contents. This should be a single serving certificate, not a certificate chain. Do not include a CA certificate.
- `destination_ca_certificate` (String) destinationCACertificate provides the contents of the ca certificate of the final destination. When using reencrypt termination this file should be provided in order to have routers use it for health checks on the secure connection. If this field is not specified, the router may provide its own destination CA and perform hostname validation using the short service name (service.namespace.svc), which allows infrastructure generated certificates to automatically verify.
- `insecure_edge_termination_policy` (String) insecureEdgeTerminationPolicy indicates the desired behavior for insecure connections to a route. While each router may make its own decisions on which ports to expose, this is normally port 80. * Allow - traffic is sent to the server on the insecure port (default) * Disable - no traffic is allowed on the insecure port. * Redirect - clients are redirected to the secure port.
- `external_certificate` (Attributes) externalCertificate provides certificate contents as a secret reference. This should be a single serving certificate, not a certificate chain. Do not include a CA certificate. The secret referenced should be present in the same namespace as that of the Route. Forbidden when 'certificate' is set. (see [below for nested schema](#nestedatt--spec--grafana--route--tls--external_certificate))
- `insecure_edge_termination_policy` (String) insecureEdgeTerminationPolicy indicates the desired behavior for insecure connections to a route. While each router may make its own decisions on which ports to expose, this is normally port 80. * Allow - traffic is sent to the server on the insecure port (edge/reencrypt terminations only) (default). * None - no traffic is allowed on the insecure port. * Redirect - clients are redirected to the secure port.
- `key` (String) key provides key file contents

<a id="nestedatt--spec--grafana--route--tls--external_certificate"></a>
### Nested Schema for `spec.grafana.route.tls.external_certificate`

Optional:

- `name` (String) name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names





Expand Down Expand Up @@ -802,16 +820,25 @@ Optional:

Required:

- `termination` (String) termination indicates termination type.
- `termination` (String) termination indicates termination type. * edge - TLS termination is done by the router and http is used to communicate with the backend (default) * passthrough - Traffic is sent straight to the destination without the router providing TLS termination * reencrypt - TLS termination is done by the router and https is used to communicate with the backend Note: passthrough termination is incompatible with httpHeader actions

Optional:

- `ca_certificate` (String) caCertificate provides the cert authority certificate contents
- `certificate` (String) certificate provides certificate contents
- `certificate` (String) certificate provides certificate contents. This should be a single serving certificate, not a certificate chain. Do not include a CA certificate.
- `destination_ca_certificate` (String) destinationCACertificate provides the contents of the ca certificate of the final destination. When using reencrypt termination this file should be provided in order to have routers use it for health checks on the secure connection. If this field is not specified, the router may provide its own destination CA and perform hostname validation using the short service name (service.namespace.svc), which allows infrastructure generated certificates to automatically verify.
- `insecure_edge_termination_policy` (String) insecureEdgeTerminationPolicy indicates the desired behavior for insecure connections to a route. While each router may make its own decisions on which ports to expose, this is normally port 80. * Allow - traffic is sent to the server on the insecure port (default) * Disable - no traffic is allowed on the insecure port. * Redirect - clients are redirected to the secure port.
- `external_certificate` (Attributes) externalCertificate provides certificate contents as a secret reference. This should be a single serving certificate, not a certificate chain. Do not include a CA certificate. The secret referenced should be present in the same namespace as that of the Route. Forbidden when 'certificate' is set. (see [below for nested schema](#nestedatt--spec--prometheus--route--tls--external_certificate))
- `insecure_edge_termination_policy` (String) insecureEdgeTerminationPolicy indicates the desired behavior for insecure connections to a route. While each router may make its own decisions on which ports to expose, this is normally port 80. * Allow - traffic is sent to the server on the insecure port (edge/reencrypt terminations only) (default). * None - no traffic is allowed on the insecure port. * Redirect - clients are redirected to the secure port.
- `key` (String) key provides key file contents

<a id="nestedatt--spec--prometheus--route--tls--external_certificate"></a>
### Nested Schema for `spec.prometheus.route.tls.external_certificate`

Optional:

- `name` (String) name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names





Expand Down Expand Up @@ -3242,16 +3269,25 @@ Optional:

Required:

- `termination` (String) termination indicates termination type.
- `termination` (String) termination indicates termination type. * edge - TLS termination is done by the router and http is used to communicate with the backend (default) * passthrough - Traffic is sent straight to the destination without the router providing TLS termination * reencrypt - TLS termination is done by the router and https is used to communicate with the backend Note: passthrough termination is incompatible with httpHeader actions

Optional:

- `ca_certificate` (String) caCertificate provides the cert authority certificate contents
- `certificate` (String) certificate provides certificate contents
- `certificate` (String) certificate provides certificate contents. This should be a single serving certificate, not a certificate chain. Do not include a CA certificate.
- `destination_ca_certificate` (String) destinationCACertificate provides the contents of the ca certificate of the final destination. When using reencrypt termination this file should be provided in order to have routers use it for health checks on the secure connection. If this field is not specified, the router may provide its own destination CA and perform hostname validation using the short service name (service.namespace.svc), which allows infrastructure generated certificates to automatically verify.
- `insecure_edge_termination_policy` (String) insecureEdgeTerminationPolicy indicates the desired behavior for insecure connections to a route. While each router may make its own decisions on which ports to expose, this is normally port 80. * Allow - traffic is sent to the server on the insecure port (default) * Disable - no traffic is allowed on the insecure port. * Redirect - clients are redirected to the secure port.
- `external_certificate` (Attributes) externalCertificate provides certificate contents as a secret reference. This should be a single serving certificate, not a certificate chain. Do not include a CA certificate. The secret referenced should be present in the same namespace as that of the Route. Forbidden when 'certificate' is set. (see [below for nested schema](#nestedatt--spec--server--route--tls--external_certificate))
- `insecure_edge_termination_policy` (String) insecureEdgeTerminationPolicy indicates the desired behavior for insecure connections to a route. While each router may make its own decisions on which ports to expose, this is normally port 80. * Allow - traffic is sent to the server on the insecure port (edge/reencrypt terminations only) (default). * None - no traffic is allowed on the insecure port. * Redirect - clients are redirected to the secure port.
- `key` (String) key provides key file contents

<a id="nestedatt--spec--server--route--tls--external_certificate"></a>
### Nested Schema for `spec.server.route.tls.external_certificate`

Optional:

- `name` (String) name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names




<a id="nestedatt--spec--server--service"></a>
Expand Down
Loading
Loading