Skip to content

Commit

Permalink
Use latest rook image for csv generation
Browse files Browse the repository at this point in the history
also add the make gen-latest-csv changes

Signed-off-by: Malay Kumar Parida <[email protected]>
  • Loading branch information
malayparida2000 committed Oct 19, 2023
1 parent 1b700a2 commit 85ec9ed
Show file tree
Hide file tree
Showing 12 changed files with 3,596 additions and 2,876 deletions.
60 changes: 56 additions & 4 deletions config/crd/bases/ocs.openshift.io_storageclusters.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -1266,6 +1266,38 @@ spec:
network:
description: Network represents cluster network settings
properties:
addressRanges:
description: AddressRanges specify a list of CIDRs that Rook will
apply to Ceph's 'public_network' and/or 'cluster_network' configurations.
This config section may be used for the "host" or "multus" network
providers.
nullable: true
properties:
cluster:
description: Cluster defines a list of CIDRs to use for Ceph
cluster network communication.
items:
description: "An IPv4 or IPv6 network CIDR. \n This naive
kubebuilder regex provides immediate feedback for some
typos and for a common problem case where the range spec
is forgotten (e.g., /24). Rook does in-depth validation
in code."
pattern: ^[0-9a-fA-F:.]{2,}\/[0-9]{1,3}$
type: string
type: array
public:
description: Public defines a list of CIDRs to use for Ceph
public network communication.
items:
description: "An IPv4 or IPv6 network CIDR. \n This naive
kubebuilder regex provides immediate feedback for some
typos and for a common problem case where the range spec
is forgotten (e.g., /24). Rook does in-depth validation
in code."
pattern: ^[0-9a-fA-F:.]{2,}\/[0-9]{1,3}$
type: string
type: array
type: object
connections:
description: Settings for network connections such as compression
and encryption across the wire.
Expand Down Expand Up @@ -1336,15 +1368,35 @@ spec:
provider:
description: Provider is what provides network connectivity to
the cluster e.g. "host" or "multus"
enum:
- ""
- host
- multus
nullable: true
type: string
selectors:
additionalProperties:
type: string
description: Selectors string values describe what networks will
be used to connect the cluster. Meanwhile the keys describe
each network respective responsibilities or any metadata storage
provider decide.
description: "Selectors define NetworkAttachmentDefinitions to
be used for Ceph public and/or cluster networks when the \"multus\"
network provider is used. This config section is not used for
other network providers. \n Valid keys are \"public\" and \"cluster\".
Refer to Ceph networking documentation for more: https://docs.ceph.com/en/reef/rados/configuration/network-config-ref/
\n Refer to Multus network annotation documentation for help
selecting values: https://github.com/k8snetworkplumbingwg/multus-cni/blob/master/docs/how-to-use.md#run-pod-with-network-annotation
\n Rook will make a best-effort attempt to automatically detect
CIDR address ranges for given network attachment definitions.
Rook's methods are robust but may be imprecise for sufficiently
complicated networks. Rook's auto-detection process obtains
a new IP address lease for each CephCluster reconcile. If Rook
fails to detect, incorrectly detects, only partially detects,
or if underlying networks do not support reusing old IP addresses,
it is best to use the 'addressRanges' config section to specify
CIDR ranges for the Ceph cluster. \n As a contrived example,
one can use a theoretical Kubernetes-wide network for Ceph client
traffic and a theoretical Rook-only network for Ceph replication
traffic as shown: selectors: public: \"default/cluster-fast-net\"
cluster: \"rook-ceph/ceph-backend-net\""
nullable: true
type: object
type: object
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -1266,6 +1266,38 @@ spec:
network:
description: Network represents cluster network settings
properties:
addressRanges:
description: AddressRanges specify a list of CIDRs that Rook will
apply to Ceph's 'public_network' and/or 'cluster_network' configurations.
This config section may be used for the "host" or "multus" network
providers.
nullable: true
properties:
cluster:
description: Cluster defines a list of CIDRs to use for Ceph
cluster network communication.
items:
description: "An IPv4 or IPv6 network CIDR. \n This naive
kubebuilder regex provides immediate feedback for some
typos and for a common problem case where the range spec
is forgotten (e.g., /24). Rook does in-depth validation
in code."
pattern: ^[0-9a-fA-F:.]{2,}\/[0-9]{1,3}$
type: string
type: array
public:
description: Public defines a list of CIDRs to use for Ceph
public network communication.
items:
description: "An IPv4 or IPv6 network CIDR. \n This naive
kubebuilder regex provides immediate feedback for some
typos and for a common problem case where the range spec
is forgotten (e.g., /24). Rook does in-depth validation
in code."
pattern: ^[0-9a-fA-F:.]{2,}\/[0-9]{1,3}$
type: string
type: array
type: object
connections:
description: Settings for network connections such as compression
and encryption across the wire.
Expand Down Expand Up @@ -1336,15 +1368,35 @@ spec:
provider:
description: Provider is what provides network connectivity to
the cluster e.g. "host" or "multus"
enum:
- ""
- host
- multus
nullable: true
type: string
selectors:
additionalProperties:
type: string
description: Selectors string values describe what networks will
be used to connect the cluster. Meanwhile the keys describe
each network respective responsibilities or any metadata storage
provider decide.
description: "Selectors define NetworkAttachmentDefinitions to
be used for Ceph public and/or cluster networks when the \"multus\"
network provider is used. This config section is not used for
other network providers. \n Valid keys are \"public\" and \"cluster\".
Refer to Ceph networking documentation for more: https://docs.ceph.com/en/reef/rados/configuration/network-config-ref/
\n Refer to Multus network annotation documentation for help
selecting values: https://github.com/k8snetworkplumbingwg/multus-cni/blob/master/docs/how-to-use.md#run-pod-with-network-annotation
\n Rook will make a best-effort attempt to automatically detect
CIDR address ranges for given network attachment definitions.
Rook's methods are robust but may be imprecise for sufficiently
complicated networks. Rook's auto-detection process obtains
a new IP address lease for each CephCluster reconcile. If Rook
fails to detect, incorrectly detects, only partially detects,
or if underlying networks do not support reusing old IP addresses,
it is best to use the 'addressRanges' config section to specify
CIDR ranges for the Ceph cluster. \n As a contrived example,
one can use a theoretical Kubernetes-wide network for Ceph client
traffic and a theoretical Rook-only network for Ceph replication
traffic as shown: selectors: public: \"default/cluster-fast-net\"
cluster: \"rook-ceph/ceph-backend-net\""
nullable: true
type: object
type: object
Expand Down
Loading

0 comments on commit 85ec9ed

Please sign in to comment.