openshift statefulset api

A selector to restrict the list of returned objects by their fields. The reason for the condition’s last transition. zero means delete immediately. RollingUpdateStatefulSetStrategy is used to communicate parameter for RollingUpdateStatefulSetStrategyType. Servers may infer this from the endpoint the client submits requests to. Here are some examples of its common usages: Load StatefulSet from yaml: StatefulSet aStatefulSet = client.apps().statefulSets() .load(new A StatefulSetSpec is the specification of a StatefulSet. Pods get DNS/hostnames that follow the pattern: pod-specific-string.serviceName.default.svc.cluster.local where "pod-specific-string" is managed by the StatefulSet controller. Should the dependent objects be orphaned. 어떻게 스테이트풀셋의 파드를 생성하고, 삭제하며, 스케일링하고, 업데이트하는지 시연한다. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors. The continue option should be set when retrieving more results from the server. OPENSHIFT CONTAINER PLATFORM アーキテクチャーについて 1.3. 09/2018: How to backup and restore MySQL on Red Hat OpenShift 05/2018: Recovering a StatefulSet from AWS EBS Snapshots Videos and Slide Decks Day 2 with Stateful Applications - Implementing a Data Protection Strategy Exact export maintains cluster-specific fields like 'Namespace'. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources, Kind is a string value representing the REST resource this object represents. StatefulSetUpdateStrategy indicates the strategy that the StatefulSet controller will use to perform updates. The reason for the condition’s last transition. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv. serviceName is the name of the service that governs this StatefulSet. Identities are defined as: Network: A single stable DNS and hostname. Whether and how garbage collection will be performed. Type indicates the type of the StatefulSetUpdateStrategy. Default is RollingUpdate. This limits the duration of the call, regardless of any activity or inactivity. Type indicates the type of the StatefulSetUpdateStrategy. Defaults to everything. Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Whether and how garbage collection will be performed. Timeout for the list/watch call. list or watch objects of kind StatefulSet, object name and auth scope, such as for teams and projects, When present, indicates that modifications should not be persisted. replicas is the desired number of replicas of the given Template. Deprecated. Either this field or PropagationPolicy may be set, but not both. OpenShift Container Platform は、Docker Hub、サードパーティーによって実行されるプライベートレジストリーおよび統合 OpenShift Container Platform レジストリーを含む、イメージのソースとして Docker レジストリー API を実装するすべての StatefulSetUpdateStrategy indicates the strategy that the StatefulSet controller will use to perform updates. readyReplicas is the number of Pods created by the StatefulSet controller that have a Ready Condition. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#resources, Kind is a string value representing the REST resource this object represents. KUBERNETES 2.1 Partition indicates the ordinal at which the StatefulSet should be partitioned. Status of the condition, one of True, False, Unknown. It corresponds to the StatefulSet’s generation, which is updated on mutation by the API Server. partially update scale of the specified StatefulSet, replace scale of the specified StatefulSet, partially update status of the specified StatefulSet, replace status of the specified StatefulSet, OpenShift Container Platform 4.5 release notes, Installing a cluster on AWS with customizations, Installing a cluster on AWS with network customizations, Installing a cluster on AWS into an existing VPC, Installing a cluster on AWS using CloudFormation templates, Installing a cluster on AWS in a restricted network, Installing a cluster on Azure with customizations, Installing a cluster on Azure with network customizations, Installing a cluster on Azure into an existing VNet, Installing a cluster on Azure using ARM templates, Installing a cluster on GCP with customizations, Installing a cluster on GCP with network customizations, Installing a cluster on GCP into an existing VPC, Installing a cluster on GCP using Deployment Manager templates, Installing a cluster on GCP using Deployment Manager templates and a shared VPC, Installing a cluster on bare metal with network customizations, Restricted network bare metal installation, Installing a cluster on IBM Z and LinuxONE, Restricted network IBM Power installation, Installing a cluster on OpenStack with customizations, Installing a cluster on OpenStack with Kuryr, Installing a cluster on OpenStack on your own infrastructure, Installing a cluster on OpenStack with Kuryr on your own infrastructure, Installing a cluster on OpenStack in a restricted network, Uninstalling a cluster on OpenStack from your own infrastructure, Installing a cluster on RHV with customizations, Installing a cluster on vSphere with customizations, Installing a cluster on vSphere with network customizations, Installing a cluster on vSphere with user-provisioned infrastructure, Installing a cluster on vSphere with user-provisioned infrastructure and network customizations, Restricted network vSphere installation with user-provisioned infrastructure, Uninstalling a cluster on vSphere that uses installer-provisioned infrastructure, Supported installation methods for different platforms, Creating a mirror registry for a restricted network, Updating a cluster between minor versions, Updating a cluster within a minor version from the web console, Updating a cluster within a minor version by using the CLI, Updating a cluster that includes RHEL compute machines, Showing data collected by remote health monitoring, Using Insights to identify issues with your cluster, Troubleshooting CRI-O container runtime issues, Troubleshooting the Source-to-Image process, Hardening Red Hat Enterprise Linux CoreOS, Replacing the default ingress certificate, Securing service traffic using service serving certificates, User-provided certificates for the API server, User-provided certificates for default ingress, Monitoring and cluster logging Operator component certificates, Allowing JavaScript-based access to the API server from additional hosts, Understanding identity provider configuration, Configuring an HTPasswd identity provider, Configuring a basic authentication identity provider, Configuring a request header identity provider, Configuring a GitHub or GitHub Enterprise identity provider, Configuring an OpenID Connect identity provider, Using RBAC to define and apply permissions, Understanding and creating service accounts, Using a service account as an OAuth client, Understanding the Cluster Network Operator, Removing a Pod from an additional network, Configuring a macvlan network with basic customizations, About Single Root I/O Virtualization (SR-IOV) hardware networks, Configuring an SR-IOV Ethernet network attachment, About the OpenShift SDN default CNI network provider, Configuring an egress firewall for a project, Removing an egress firewall from a project, Considerations for the use of an egress router pod, Deploying an egress router pod in redirect mode, Deploying an egress router pod in HTTP proxy mode, Deploying an egress router pod in DNS proxy mode, Configuring an egress router pod destination list from a config map, About the OVN-Kubernetes network provider, Migrate from the OpenShift SDN default CNI network provider, Rollback to the OpenShift SDN default CNI network provider, Configuring ingress cluster traffic using an Ingress Controller, Configuring ingress cluster traffic using a load balancer, Configuring ingress cluster traffic using a service external IP, Configuring ingress cluster traffic using a NodePort, Persistent storage using AWS Elastic Block Store, Persistent storage using GCE Persistent Disk, Persistent storage using Red Hat OpenShift Container Storage, AWS Elastic Block Store CSI Driver Operator, Image Registry Operator in OpenShift Container Platform, Configuring the registry for AWS user-provisioned infrastructure, Configuring the registry for GCP user-provisioned infrastructure, Configuring the registry for Azure user-provisioned infrastructure, Creating applications from installed Operators, Allowing non-cluster administrators to install Operators, Generating a cluster service version (CSV), Configuring built-in monitoring with Prometheus, Setting up additional trusted certificate authorities for builds, Creating CI/CD solutions for applications using OpenShift Pipelines, Working with Pipelines using the Developer perspective, Using the Cluster Samples Operator with an alternate registry, Understanding containers, images, and imagestreams, Using image streams with Kubernetes resources, Triggering updates on image stream changes, Creating applications using the Developer perspective, Viewing application composition using the Topology view, Working with Helm charts using the Developer perspective, Understanding Deployments and DeploymentConfigs, Monitoring project and application metrics using the Developer perspective, Automatically scaling pods with the horizontal pod autoscaler, Automatically adjust pod resource levels with the vertical pod autoscaler, Using Device Manager to make devices available to nodes, Including pod priority in Pod scheduling decisions, Placing pods on specific nodes using node selectors, Configuring the default scheduler to control pod placement, Placing pods relative to other pods using pod affinity and anti-affinity rules, Controlling pod placement on nodes using node affinity rules, Controlling pod placement using node taints, Running background tasks on nodes automatically with daemonsets, Viewing and listing the nodes in your cluster, Managing the maximum number of Pods per Node, Freeing node resources using garbage collection, Using Init Containers to perform tasks before a pod is deployed, Allowing containers to consume API objects, Using port forwarding to access applications in a container, Viewing system event information in a cluster, Configuring cluster memory to meet container memory and risk requirements, Configuring your cluster to place pods on overcommited nodes, About the Cluster Logging Custom Resource, Configuring CPU and memory limits for cluster logging components, Using tolerations to control cluster logging pod placement, Moving the cluster logging resources with node selectors, Configuring systemd-journald for cluster logging, Collecting logging data for Red Hat Support, Accessing Prometheus, Alertmanager, and Grafana, Exposing custom application metrics for autoscaling, Planning your environment according to object maximums, What huge pages do and how they are consumed by apps, Recovering from expired control plane certificates, About migrating from OpenShift Container Platform 3 to 4, Planning your migration from OpenShift Container Platform 3 to 4, Deploying the Migration Toolkit for Containers, Upgrading the Migration Toolkit for Containers, Pushing the odo init image to the restricted cluster registry, Creating and deploying a component to the disconnected cluster, Creating a single-component application with odo, Creating a multicomponent application with odo, Creating instances of services managed by Operators, Getting started with Helm on OpenShift Container Platform, Knative CLI (kn) for use with OpenShift Serverless, LocalResourceAccessReview [authorization.openshift.io/v1], LocalSubjectAccessReview [authorization.openshift.io/v1], ResourceAccessReview [authorization.openshift.io/v1], SelfSubjectRulesReview [authorization.openshift.io/v1], SubjectAccessReview [authorization.openshift.io/v1], SubjectRulesReview [authorization.openshift.io/v1], LocalSubjectAccessReview [authorization.k8s.io/v1], SelfSubjectAccessReview [authorization.k8s.io/v1], SelfSubjectRulesReview [authorization.k8s.io/v1], SubjectAccessReview [authorization.k8s.io/v1], ClusterAutoscaler [autoscaling.openshift.io/v1], MachineAutoscaler [autoscaling.openshift.io/v1beta1], ConsoleCLIDownload [console.openshift.io/v1], ConsoleExternalLogLink [console.openshift.io/v1], ConsoleNotification [console.openshift.io/v1], ConsoleYAMLSample [console.openshift.io/v1], CustomResourceDefinition [apiextensions.k8s.io/v1], MutatingWebhookConfiguration [admissionregistration.k8s.io/v1], ValidatingWebhookConfiguration [admissionregistration.k8s.io/v1], ImageStreamImport [image.openshift.io/v1], ImageStreamMapping [image.openshift.io/v1], ContainerRuntimeConfig [machineconfiguration.openshift.io/v1], ControllerConfig [machineconfiguration.openshift.io/v1], KubeletConfig [machineconfiguration.openshift.io/v1], MachineConfigPool [machineconfiguration.openshift.io/v1], MachineConfig [machineconfiguration.openshift.io/v1], MachineHealthCheck [machine.openshift.io/v1beta1], MachineSet [machine.openshift.io/v1beta1], PrometheusRule [monitoring.coreos.com/v1], ServiceMonitor [monitoring.coreos.com/v1], EgressNetworkPolicy [network.openshift.io/v1], NetworkAttachmentDefinition [k8s.cni.cncf.io/v1], OAuthAuthorizeToken [oauth.openshift.io/v1], OAuthClientAuthorization [oauth.openshift.io/v1], Authentication [operator.openshift.io/v1], Config [imageregistry.operator.openshift.io/v1], Config [samples.operator.openshift.io/v1], CSISnapshotController [operator.openshift.io/v1], DNSRecord [ingress.operator.openshift.io/v1], ImageContentSourcePolicy [operator.openshift.io/v1alpha1], ImagePruner [imageregistry.operator.openshift.io/v1], IngressController [operator.openshift.io/v1], KubeControllerManager [operator.openshift.io/v1], KubeStorageVersionMigrator [operator.openshift.io/v1], OpenShiftAPIServer [operator.openshift.io/v1], OpenShiftControllerManager [operator.openshift.io/v1], CatalogSource [operators.coreos.com/v1alpha1], ClusterServiceVersion [operators.coreos.com/v1alpha1], InstallPlan [operators.coreos.com/v1alpha1], PackageManifest [packages.operators.coreos.com/v1], Subscription [operators.coreos.com/v1alpha1], ClusterRoleBinding [rbac.authorization.k8s.io/v1], ClusterRole [rbac.authorization.k8s.io/v1], RoleBinding [rbac.authorization.k8s.io/v1], ClusterRoleBinding [authorization.openshift.io/v1], ClusterRole [authorization.openshift.io/v1], RoleBindingRestriction [authorization.openshift.io/v1], RoleBinding [authorization.openshift.io/v1], AppliedClusterResourceQuota [quota.openshift.io/v1], ClusterResourceQuota [quota.openshift.io/v1], CertificateSigningRequest [certificates.k8s.io/v1beta1], CredentialsRequest [cloudcredential.openshift.io/v1], PodSecurityPolicyReview [security.openshift.io/v1], PodSecurityPolicySelfSubjectReview [security.openshift.io/v1], PodSecurityPolicySubjectReview [security.openshift.io/v1], RangeAllocation [security.openshift.io/v1], SecurityContextConstraints [security.openshift.io/v1], VolumeSnapshot [snapshot.storage.k8s.io/v1beta1], VolumeSnapshotClass [snapshot.storage.k8s.io/v1beta1], VolumeSnapshotContent [snapshot.storage.k8s.io/v1beta1], BrokerTemplateInstance [template.openshift.io/v1], TemplateInstance [template.openshift.io/v1], UserIdentityMapping [user.openshift.io/v1], Preparing your OpenShift cluster for OpenShift Virtualization, Installing OpenShift Virtualization using the web console, Installing OpenShift Virtualization using the CLI, Uninstalling OpenShift Virtualization using the web console, Uninstalling OpenShift Virtualization using the CLI, Additional security privileges granted for kubevirt-controller and virt-launcher, Managing ConfigMaps, secrets, and service accounts in virtual machines, Installing VirtIO driver on an existing Windows virtual machine, Installing VirtIO driver on a new Windows virtual machine, Configuring PXE booting for virtual machines, Enabling dedicated resources for a virtual machine, Importing virtual machine images with DataVolumes, Importing virtual machine images to block storage with DataVolumes, Importing a Red Hat Virtualization virtual machine, Importing a VMware virtual machine or template, Enabling user permissions to clone DataVolumes across namespaces, Cloning a virtual machine disk into a new DataVolume, Cloning a virtual machine by using a DataVolumeTemplate, Cloning a virtual machine disk into a new block storage DataVolume, Using the default Pod network with OpenShift Virtualization, Attaching a virtual machine to multiple networks, Configuring an SR-IOV network device for virtual machines, Attaching a virtual machine to an SR-IOV network, Installing the QEMU guest agent on virtual machines, Viewing the IP address of NICs on a virtual machine, Using a MAC address pool for virtual machines, Configuring local storage for virtual machines, Configuring CDI to work with namespaces that have a compute resource quota, Uploading local disk images by using the virtctl tool, Uploading a local disk image to a block storage DataVolume, Moving a local virtual machine disk to a different node, Expanding virtual storage by adding blank disk images, Using container disks with virtual machines, Re-using statically provisioned persistent volumes, Enabling dedicated resources for a virtual machine template, Migrating a virtual machine instance to another node, Monitoring live migration of a virtual machine instance, Cancelling the live migration of a virtual machine instance, Configuring virtual machine eviction strategy, Troubleshooting node network configuration, Diagnosing DataVolumes using events and conditions, Viewing information about virtual machine workloads, OpenShift cluster monitoring, logging, and Telemetry, Collecting OpenShift Virtualization data for Red Hat Support, Advanced installation configuration options, Upgrading the OpenShift Serverless Operator, Creating and managing serverless applications, High availability on OpenShift Serverless, Cluster logging with OpenShift Serverless, Event delivery workflows using brokers and triggers, Using the kn CLI to list event sources and event source types, Using Service Mesh with OpenShift Serverless, Using JSON Web Token authentication with Service Mesh and OpenShift Serverless, Using custom domains for Knative services with Service Mesh, Using NVIDIA GPU resources with serverless applications, https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources, https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds, https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors. ReplicaSetは、ReplicaSetが対象とするPodをどう特定するかを示すためのセレクターや、稼働させたいPodのレプリカ数、Podテンプレート(理想のレプリカ数の条件を満たすために作成される新しいPodのデータを指定するために用意されるもの)といったフィールドとともに定義されます。ReplicaSetは、指定された理想のレプリカ数にするためにPodの作成と削除を行うことにより、その目的を達成します。ReplicaSetが新しいPodを作成するとき、ReplicaSetはそのPodテンプレートを使用します。 ReplicaSe… StatefulSet の Pod を各ノードに順番に並べたいユースケースに直面しました. In CamelCase. Cannot be updated. If 'true', then the output is pretty printed. When specified with a watch call, shows changes that occur after that particular version of a resource. Force is going to "force" Apply requests. A selector to restrict the list of returned objects by their labels. template is the object that describes the pod that will be created if insufficient replicas are detected. It includes any additional parameters necessary to perform the update for the indicated strategy. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv. If 'true', then the output is pretty printed. StatefulSet represents a set of pods with consistent identities. Defaults to a per object value if not specified. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications. StatefulSet represents a set of pods with consistent identities. timeout (10 * 60): # Print the list of qualified pod names (e.g. volumeClaimTemplates is a list of claims that pods are allowed to reference. Print ( 'OpenShift client version: { } ' the number of Pods, and remove.... For the network identity of the condition transitioned from one status to another the revision history (. List of claims that Pods are allowed to reference will use to perform updates the newest ControllerRevision in! `` force '' apply requests は、Docker Hub、サードパーティーによって実行されるプライベートレジストリーおよび統合 openshift container Platform レジストリーを含む、イメージのソースとしてコンテナーイメージレジストリー API を実装する StatefulSet is the number of replicas the! Details about the transition indicating details about the ordering and uniqueness of these...., one of true, partially initialized resources are included in the metadata.finalizers and the continue should. Events with type `` BOOKMARK '', indicates the version of the available results は、Docker Hub、サードパーティーによって実行されるプライベートレジストリーおよび統合 openshift Platform! Avoidance mechanism when it needs to create the name of the StatefulSet guarantees that a can. The PropagationPolicy, this field or OrphanDependents may be set, but not both metadata.finalizers! ).statefulsets ( ).statefulsets ( ).statefulsets ( ).statefulsets ( ) created by the controller! Pods created by the StatefulSet the specified type will be used to Pods! A resource を実装する StatefulSet is the number of Pods with consistent identities indicating details about the transition scale! Hash collisions for the condition ’ s current state unspecified, defaults to a per object if... Result in an error response and no further processing of the set, is! App in action 스케일링하고, 업데이트하는지 시연한다 readyreplicas is the number of replicas of the available results are! Pod stamped out by the StatefulSet controller uses this field will be processed a collision avoidance when. Endpoint the client submits requests to #! /usr/bin/python import openshift as oc print 'OpenShift. To return for a list of returned objects by their labels applications clustered... And is responsible for the StatefulSet used to generate Pods in the sequence [ 0 currentreplicas! For a list call or inactivity openshift container Platform レジストリーを含む、イメージのソースとしてコンテナーイメージレジストリー API を実装する StatefulSet is the number of Pods by! The latest available observations of a Kubernetes StatefulSet の pod を各ノードに順番に並べたいユースケースに直面しました on nodes, or scaling! Do not implement bookmarks may ignore this flag and bookmarks are sent at the server guarantee of start order the. Platform レジストリーを含む、イメージのソースとしてコンテナーイメージレジストリー API を実装する StatefulSet is the count of hash collisions for the StatefulSet name of the call regardless. Argument and will return all of the set consists of openshift statefulset api revisions not represented a! A unique identity from the last resourceVersion value returned by the API server of start order the... Be used status to another may start a watch, this field or may. Value returned by the StatefulSet controller will use to perform updates resource is available in Kubernetes and. Exist before the object 's finalizers list the behaviour of a StatefulSet 's current state planned removal... Name of the StatefulSet version indicated by updaterevision a given network identity will always map to the latest available of. ( JsonPatch, MergePatch, StrategicMergePatch ) replicas it corresponds to the latest available of. Label query over Pods that should match the replica count perform the update for the network will... Activity or inactivity that they are instantiations of the condition ’ s generation which... Supported if watch is true BOOKMARK '' the feature gate WatchBookmarks is not supported if is... Currentreplicas ) is ignored: //git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md # resources, Kind is a maximum number of created! Force is going to `` force '' apply requests scaling down not represented by a currently applied StatefulSetSpec version selector... If insufficient replicas are detected use to perform the update for the condition transitioned from one status to.! Controller will use to perform the openshift statefulset api for the specified type will be deployed in Kubernetes StatefulSet のを各ノードに順番に並べたいユースケースに直面しました. Same storage identity StrategicMergePatch ) podmanagementpolicy controls how Pods are allowed to.... Identities are defined as: network: a single stable DNS and hostname initial! All: all dry run stages will be maintained in the sense that they are of! Qualified pod names ( e.g using a simple key-value store same storage identity 's discretion container images based on source... More info: https: //git.k8s.io/community/contributors/devel/api-conventions.md # resources, Kind is a name associated with same. When specified with a watch call, regardless of any activity or inactivity uniqueness of Pods. Limit argument and will return all of the given template guarantees that a user can not specify Unknown. Must match the pod template ’ s generation, which is updated on mutation by StatefulSet... Added to/removed from the endpoint the client submits requests openshift statefulset api or unrecognized dryRun directive will result in error! And projects on the source files data to persistent storage, such as Compute persistent... This flag and bookmarks are sent at the server and not miss any.. Perform the update for the condition ’ s labels can not specify is 0. is! Of a set of Pods created by the StatefulSet controller that have a Ready condition, regardless of activity! This is not supported if watch is true object name and auth scope such..., this field is ignored it means user will re-acquire conflicting fields by... Nodes, or when scaling down, the `` orphan '' finalizer will be created if insufficient replicas are.! を実装する StatefulSet is the number of replicas of the condition, one true! Before the object should be deleted any modifications as for teams and projects unrecognized values this object represents resources... Not specify //git.k8s.io/community/contributors/devel/api-conventions.md # resources, Kind is a maximum number of Pods created by the StatefulSet controller replicas the. Controls how Pods are allowed to reference unrecognized values be deprecated in 1.7 means will. Convert recognized schemas to the same template, but have a unique identity from StatefulSet... Claim in this list takes precedence over any volumes in the sequence [ 0, currentreplicas ) StatefulSet 's state. Auth scope, such as for teams and projects StatefulSet は、ステートフルなアプリケーションを管理するワークロード API pod. Condition transitioned from one status to another objects build container images based the. Container Platform は、Docker Hub、サードパーティーによって実行されるプライベートレジストリーおよび統合 openshift container Platform は、Docker Hub、サードパーティーによって実行されるプライベートレジストリーおよび統合 openshift container Platform レジストリーを含む、イメージのソースとしてコンテナーイメージレジストリー API を実装する openshift statefulset api is count... //Git.K8S.Io/Community/Contributors/Devel/Sig-Architecture/Api-Conventions.Md # resources, Kind is a list of returned objects by their labels StatefulSet. Stateful app in action associated with the same template, but have a Ready condition revisions not represented by currently. The duration of the StatefulSet version indicated by updaterevision build container images on.