HealthCheck is the Schema for the HealthChecks API. Health Checks determine whether instances are responsive and able to do work.
Type
CRD
Group
compute.gcp.upbound.io
Version
v1beta1
apiVersion: compute.gcp.upbound.io/v1beta1
kind: HealthCheck
HealthCheckSpec defines the desired state of HealthCheck
No description provided.
A nested object resource Structure is documented below.
A nested object resource Structure is documented below.
A nested object resource Structure is documented below.
A nested object resource Structure is documented below.
Configure logging on this health check. Structure is documented below.
A nested object resource Structure is documented below.
A nested object resource Structure is documented below.
THIS IS AN ALPHA FIELD. Do not use it in production. It is not honored unless the relevant Crossplane feature flag is enabled, and may be changed or removed without notice. InitProvider holds the same fields as ForProvider, with the exception of Identifier and other resource reference fields. The fields that are in InitProvider are merged into ForProvider when the resource is created. The same fields are also added to the terraform ignore_changes hook, to avoid updating them after creation. This is useful for fields that are required on creation, but we do not desire to update them after creation, for example because of an external controller is managing them, like an autoscaler.
A nested object resource Structure is documented below.
A nested object resource Structure is documented below.
A nested object resource Structure is documented below.
A nested object resource Structure is documented below.
Configure logging on this health check. Structure is documented below.
A nested object resource Structure is documented below.
A nested object resource Structure is documented below.
THIS IS AN ALPHA FIELD. Do not use it in production. It is not honored unless the relevant Crossplane feature flag is enabled, and may be changed or removed without notice. ManagementPolicies specify the array of actions Crossplane is allowed to take on the managed and external resources. This field is planned to replace the DeletionPolicy field in a future release. Currently, both could be set independently and non-default values would be honored if the feature flag is enabled. If both are custom, the DeletionPolicy field will be ignored. See the design doc for more information: https://github.com/crossplane/crossplane/blob/499895a25d1a1a0ba1604944ef98ac7a1a71f197/design/design-doc-observe-only-resources.md?plain=1#L223 and this one: https://github.com/crossplane/crossplane/blob/444267e84783136daa93568b364a5f01228cacbe/design/one-pager-ignore-changes.md
ProviderConfigReference specifies how the provider that will be used to create, observe, update, and delete this managed resource should be configured.
Policies for referencing.
ProviderReference specifies the provider that will be used to create, observe, update, and delete this managed resource. Deprecated: Please use ProviderConfigReference, i.e. providerConfigRef
Policies for referencing.
PublishConnectionDetailsTo specifies the connection secret config which contains a name, metadata and a reference to secret store config to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource.
WriteConnectionSecretToReference specifies the namespace and name of a Secret to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource. This field is planned to be replaced in a future release in favor of PublishConnectionDetailsTo. Currently, both could be set independently and connection details would be published to both without affecting each other.
HealthCheckStatus defines the observed state of HealthCheck.
No description provided.
A nested object resource Structure is documented below.
A nested object resource Structure is documented below.
A nested object resource Structure is documented below.
A nested object resource Structure is documented below.
Configure logging on this health check. Structure is documented below.
A nested object resource Structure is documented below.
A nested object resource Structure is documented below.
Conditions of the resource.
forwarding-rule
apiVersion: compute.gcp.upbound.io/v1beta1
kind: HealthCheck
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/forwardingrule
labels:
testing.upbound.io/example-name: forwarding-rule
name: forwarding-rule
spec:
forProvider:
checkIntervalSec: 1
tcpHealthCheck:
- port: 80
timeoutSec: 1
urlmap
apiVersion: compute.gcp.upbound.io/v1beta1
kind: HealthCheck
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/urlmap
labels:
testing.upbound.io/example-name: urlmap
name: urlmap
spec:
forProvider:
checkIntervalSec: 1
httpHealthCheck:
- port: 80
timeoutSec: 1
backend-service
apiVersion: compute.gcp.upbound.io/v1beta1
kind: HealthCheck
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/backendservicesignedurlkey
labels:
testing.upbound.io/example-name: backend-service
name: backend-service
spec:
forProvider:
checkIntervalSec: 1
httpHealthCheck:
- port: 80
timeoutSec: 1
autoscaler
apiVersion: compute.gcp.upbound.io/v1beta1
kind: HealthCheck
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/autoscaler
labels:
testing.upbound.io/example-name: autoscaler
name: autoscaler
spec:
forProvider:
checkIntervalSec: 1
tcpHealthCheck:
- port: 80
timeoutSec: 1
region-instance-group-manager
apiVersion: compute.gcp.upbound.io/v1beta1
kind: HealthCheck
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/regioninstancegroupmanager
labels:
testing.upbound.io/example-name: region-instance-group-manager
name: region-instance-group-manager
spec:
forProvider:
checkIntervalSec: 1
httpHealthCheck:
- port: 80
timeoutSec: 1
target-tcp-proxy
apiVersion: compute.gcp.upbound.io/v1beta1
kind: HealthCheck
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/targettcpproxy
labels:
testing.upbound.io/example-name: target-tcp-proxy
name: target-tcp-proxy
spec:
forProvider:
checkIntervalSec: 1
tcpHealthCheck:
- port: 443
timeoutSec: 1
backend-service
apiVersion: compute.gcp.upbound.io/v1beta1
kind: HealthCheck
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/backendservice
labels:
testing.upbound.io/example-name: backend-service
name: backend-service
spec:
forProvider:
checkIntervalSec: 1
httpHealthCheck:
- port: 80
timeoutSec: 1
target-ssl-proxy
apiVersion: compute.gcp.upbound.io/v1beta1
kind: HealthCheck
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/targetsslproxy
labels:
testing.upbound.io/example-name: target-ssl-proxy
name: target-ssl-proxy
spec:
forProvider:
checkIntervalSec: 1
tcpHealthCheck:
- port: 443
timeoutSec: 1
health-check
apiVersion: compute.gcp.upbound.io/v1beta1
kind: HealthCheck
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/healthcheck
labels:
testing.upbound.io/example-name: health-check
name: health-check
spec:
forProvider:
checkIntervalSec: 1
tcpHealthCheck:
- port: 80
timeoutSec: 1
global-forwarding-rule
apiVersion: compute.gcp.upbound.io/v1beta1
kind: HealthCheck
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/globalforwardingrule
labels:
testing.upbound.io/example-name: global-forwarding-rule
name: global-forwarding-rule
spec:
forProvider:
checkIntervalSec: 1
tcpHealthCheck:
- port: 443
timeoutSec: 1
instance-group-manager
apiVersion: compute.gcp.upbound.io/v1beta1
kind: HealthCheck
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/instancegroupmanager
labels:
testing.upbound.io/example-name: instance-group-manager
name: instance-group-manager
spec:
forProvider:
checkIntervalSec: 1
tcpHealthCheck:
- port: 443
timeoutSec: 1