Runtime is the Schema for the Runtimes API. A Cloud AI Platform Notebook runtime.
Type
CRD
Group
notebooks.gcp.upbound.io
Version
v1beta1
apiVersion: notebooks.gcp.upbound.io/v1beta1
kind: Runtime
RuntimeSpec defines the desired state of Runtime
No description provided.
The config settings for accessing runtime. Structure is documented below.
The config settings for software inside the runtime. Structure is documented below.
Use a list of container images to use as Kernels in the notebook instance. Structure is documented below.
Use a Compute Engine VM image to start the managed notebook instance. Structure is documented below.
Virtual Machine configuration settings. Structure is documented below.
Use a list of container images to start the notebook instance. Structure is documented below.
Data disk option configuration settings. Structure is documented below.
Input only. Specifies the parameters for a new disk that will be created alongside the new instance. Use initialization parameters to create boot disks or local SSDs attached to the new instance. This property is mutually exclusive with the source property; you can only define one or the other, but not both. Structure is documented below.
Encryption settings for virtual machine data disk. Structure is documented below.
Shielded VM Instance configuration settings. Structure is documented below.
The Compute Engine tags to add to runtime (see [Tagging instances] (https://cloud.google.com/compute/docs/ label-or-tag-resources#tags)).
THIS IS A BETA FIELD. It will be honored unless the Management Policies feature flag is disabled. 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.
The config settings for accessing runtime. Structure is documented below.
The config settings for software inside the runtime. Structure is documented below.
Use a list of container images to use as Kernels in the notebook instance. Structure is documented below.
Use a Compute Engine VM image to start the managed notebook instance. Structure is documented below.
Virtual Machine configuration settings. Structure is documented below.
Use a list of container images to start the notebook instance. Structure is documented below.
Data disk option configuration settings. Structure is documented below.
Input only. Specifies the parameters for a new disk that will be created alongside the new instance. Use initialization parameters to create boot disks or local SSDs attached to the new instance. This property is mutually exclusive with the source property; you can only define one or the other, but not both. Structure is documented below.
Encryption settings for virtual machine data disk. Structure is documented below.
Shielded VM Instance configuration settings. Structure is documented below.
The Compute Engine tags to add to runtime (see [Tagging instances] (https://cloud.google.com/compute/docs/ label-or-tag-resources#tags)).
THIS IS A BETA FIELD. It is on by default but can be opted out through a Crossplane feature flag. 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.
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.
RuntimeStatus defines the observed state of Runtime.
No description provided.
The config settings for accessing runtime. Structure is documented below.
Contains Runtime daemon metrics such as Service status and JupyterLab status Structure is documented below.
The config settings for software inside the runtime. Structure is documented below.
Use a list of container images to use as Kernels in the notebook instance. Structure is documented below.
Use a Compute Engine VM image to start the managed notebook instance. Structure is documented below.
Virtual Machine configuration settings. Structure is documented below.
Use a list of container images to start the notebook instance. Structure is documented below.
Data disk option configuration settings. Structure is documented below.
(Output) Indicates a list of features to enable on the guest operating system. Applicable only for bootable images. To see a list of available features, read https://cloud.google.com/compute/docs/ images/create-delete-deprecate-private-images#guest-os-features options.
Input only. Specifies the parameters for a new disk that will be created alongside the new instance. Use initialization parameters to create boot disks or local SSDs attached to the new instance. This property is mutually exclusive with the source property; you can only define one or the other, but not both. Structure is documented below.
(Output) Output only. Any valid publicly visible licenses.
Encryption settings for virtual machine data disk. Structure is documented below.
Shielded VM Instance configuration settings. Structure is documented below.
The Compute Engine tags to add to runtime (see [Tagging instances] (https://cloud.google.com/compute/docs/ label-or-tag-resources#tags)).
Conditions of the resource.
runtime
apiVersion: notebooks.gcp.upbound.io/v1beta1
kind: Runtime
metadata:
annotations:
meta.upbound.io/example-id: notebooks/v1beta1/runtime
labels:
testing.upbound.io/example-name: runtime
name: runtime
spec:
forProvider:
accessConfig:
- accessType: SERVICE_ACCOUNT
runtimeOwner: ${data.google_iam_member.op-user}
location: us-central1
softwareConfig:
- enableHealthMonitoring: true
virtualMachine:
- virtualMachineConfig:
- dataDisk:
- initializeParams:
- diskSizeGb: 100
diskType: PD_STANDARD
machineType: n1-standard-4
runtime-iam-member
apiVersion: notebooks.gcp.upbound.io/v1beta1
kind: Runtime
metadata:
annotations:
meta.upbound.io/example-id: notebooks/v1beta1/runtimeiammember
labels:
testing.upbound.io/example-name: runtime-iam-member
name: runtime-iam-member
spec:
forProvider:
accessConfig:
- accessType: SERVICE_ACCOUNT
runtimeOwner: ${data.google_iam_member.op-user}
location: us-central1
softwareConfig:
- enableHealthMonitoring: true
virtualMachine:
- virtualMachineConfig:
- dataDisk:
- initializeParams:
- diskSizeGb: 100
diskType: PD_STANDARD
machineType: n1-standard-4
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.