Skip to content

Commit

Permalink
Include the operator-sdk bundle as repo payload
Browse files Browse the repository at this point in the history
It has become common practice to include the bundle folder in the repo
this patch is generated by running "make bundle", moving forward
updating the bundle will be part of the release process.
  • Loading branch information
ArangoGutierrez committed Jan 17, 2023
1 parent 080350a commit b9068bd
Show file tree
Hide file tree
Showing 12 changed files with 1,229 additions and 3 deletions.
20 changes: 20 additions & 0 deletions bundle.Dockerfile
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
FROM scratch

# Core bundle labels.
LABEL operators.operatorframework.io.bundle.mediatype.v1=registry+v1
LABEL operators.operatorframework.io.bundle.manifests.v1=manifests/
LABEL operators.operatorframework.io.bundle.metadata.v1=metadata/
LABEL operators.operatorframework.io.bundle.package.v1=nfd-operator
LABEL operators.operatorframework.io.bundle.channels.v1=alpha
LABEL operators.operatorframework.io.metrics.builder=operator-sdk-v1.26.0+git
LABEL operators.operatorframework.io.metrics.mediatype.v1=metrics+v1
LABEL operators.operatorframework.io.metrics.project_layout=go.kubebuilder.io/v3

# Labels for testing.
LABEL operators.operatorframework.io.test.mediatype.v1=scorecard+v1
LABEL operators.operatorframework.io.test.config.v1=tests/scorecard/

# Copy files to locations specified by labels.
COPY bundle/manifests /manifests/
COPY bundle/metadata /metadata/
COPY bundle/tests/scorecard /tests/scorecard/
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
apiVersion: v1
kind: Service
metadata:
creationTimestamp: null
labels:
control-plane: controller-manager
name: nfd-controller-manager-metrics-service
spec:
ports:
- name: https
port: 8443
targetPort: https
selector:
control-plane: controller-manager
status:
loadBalancer: {}
18 changes: 18 additions & 0 deletions bundle/manifests/nfd-manager-config_v1_configmap.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
apiVersion: v1
data:
controller_manager_config.yaml: |+
apiVersion: controller-runtime.sigs.k8s.io/v1alpha1
kind: ControllerManagerConfig
health:
healthProbeBindAddress: :8081
metrics:
bindAddress: 127.0.0.1:8080
webhook:
port: 9443
leaderElection:
leaderElect: true
resourceName: 39f5e5c3.nodefeaturediscoveries.nfd.kubernetes.io
kind: ConfigMap
metadata:
name: nfd-manager-config
Original file line number Diff line number Diff line change
@@ -0,0 +1,10 @@
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
creationTimestamp: null
name: nfd-metrics-reader
rules:
- nonResourceURLs:
- /metrics
verbs:
- get
530 changes: 530 additions & 0 deletions bundle/manifests/nfd-operator.clusterserviceversion.yaml

Large diffs are not rendered by default.

183 changes: 183 additions & 0 deletions bundle/manifests/nfd.kubernetes.io_nodefeaturediscoveries.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,183 @@
apiVersion: apiextensions.k8s.io/v1
kind: CustomResourceDefinition
metadata:
annotations:
api-approved.kubernetes.io: unapproved, experimental-only
controller-gen.kubebuilder.io/version: v0.8.0
creationTimestamp: null
name: nodefeaturediscoveries.nfd.kubernetes.io
spec:
group: nfd.kubernetes.io
names:
kind: NodeFeatureDiscovery
listKind: NodeFeatureDiscoveryList
plural: nodefeaturediscoveries
singular: nodefeaturediscovery
scope: Namespaced
versions:
- name: v1
schema:
openAPIV3Schema:
description: NodeFeatureDiscovery is the Schema for the nodefeaturediscoveries
API
properties:
apiVersion:
description: 'APIVersion defines the versioned schema of this representation
of an object. Servers should convert recognized schemas to the latest
internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources'
type: string
kind:
description: 'Kind is a string value representing the REST resource this
object represents. Servers may infer this from the endpoint the client
submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds'
type: string
metadata:
type: object
spec:
description: NodeFeatureDiscoverySpec defines the desired state of NodeFeatureDiscovery
properties:
extraLabelNs:
description: ExtraLabelNs defines the list of of allowed extra label
namespaces By default, only allow labels in the default `feature.node.kubernetes.io`
label namespace
items:
type: string
nullable: true
type: array
instance:
description: Instance name. Used to separate annotation namespaces
for multiple parallel deployments.
type: string
labelWhiteList:
description: LabelWhiteList defines a regular expression for filtering
feature labels based on their name. Each label must match against
the given reqular expression in order to be published.
nullable: true
type: string
operand:
description: OperandSpec describes configuration options for the operand
properties:
image:
description: Image defines the image to pull for the NFD operand
[defaults to k8s.gcr.io/nfd/node-feature-discovery]
pattern: '[a-zA-Z0-9\-]+'
type: string
imagePullPolicy:
description: ImagePullPolicy defines Image pull policy for the
NFD operand image [defaults to Always]
type: string
servicePort:
description: ServicePort specifies the TCP port that nfd-master
listens for incoming requests.
type: integer
type: object
resourceLabels:
description: ResourceLabels defines the list of features to be advertised
as extended resources instead of labels.
items:
type: string
nullable: true
type: array
topologyUpdater:
description: Deploy the NFD-Topology-Updater NFD-Topology-Updater
is a daemon responsible for examining allocated resources on a worker
node to account for resources available to be allocated to new pod
on a per-zone basis https://kubernetes-sigs.github.io/node-feature-discovery/v0.10/get-started/introduction.html#nfd-topology-updater
type: boolean
workerConfig:
description: WorkerConfig describes configuration options for the
NFD worker.
properties:
configData:
description: BinaryData holds the NFD configuration file
type: string
required:
- configData
type: object
type: object
status:
description: NodeFeatureDiscoveryStatus defines the observed state of
NodeFeatureDiscovery
properties:
conditions:
description: Conditions represents the latest available observations
of current state.
items:
description: "Condition contains details for one aspect of the current
state of this API Resource. --- This struct is intended for direct
use as an array at the field path .status.conditions. For example,
\n type FooStatus struct{ // Represents the observations of a
foo's current state. // Known .status.conditions.type are: \"Available\",
\"Progressing\", and \"Degraded\" // +patchMergeKey=type // +patchStrategy=merge
// +listType=map // +listMapKey=type Conditions []metav1.Condition
`json:\"conditions,omitempty\" patchStrategy:\"merge\" patchMergeKey:\"type\"
protobuf:\"bytes,1,rep,name=conditions\"` \n // other fields }"
properties:
lastTransitionTime:
description: lastTransitionTime is the last time the condition
transitioned from one status to another. This should be when
the underlying condition changed. If that is not known, then
using the time when the API field changed is acceptable.
format: date-time
type: string
message:
description: message is a human readable message indicating
details about the transition. This may be an empty string.
maxLength: 32768
type: string
observedGeneration:
description: observedGeneration represents the .metadata.generation
that the condition was set based upon. For instance, if .metadata.generation
is currently 12, but the .status.conditions[x].observedGeneration
is 9, the condition is out of date with respect to the current
state of the instance.
format: int64
minimum: 0
type: integer
reason:
description: reason contains a programmatic identifier indicating
the reason for the condition's last transition. Producers
of specific condition types may define expected values and
meanings for this field, and whether the values are considered
a guaranteed API. The value should be a CamelCase string.
This field may not be empty.
maxLength: 1024
minLength: 1
pattern: ^[A-Za-z]([A-Za-z0-9_,:]*[A-Za-z0-9_])?$
type: string
status:
description: status of the condition, one of True, False, Unknown.
enum:
- "True"
- "False"
- Unknown
type: string
type:
description: type of condition in CamelCase or in foo.example.com/CamelCase.
--- Many .condition.type values are consistent across resources
like Available, but because arbitrary conditions can be useful
(see .node.status.conditions), the ability to deconflict is
important. The regex it matches is (dns1123SubdomainFmt/)?(qualifiedNameFmt)
maxLength: 316
pattern: ^([a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*/)?(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])$
type: string
required:
- lastTransitionTime
- message
- reason
- status
- type
type: object
type: array
type: object
type: object
served: true
storage: true
subresources:
status: {}
status:
acceptedNames:
kind: ""
plural: ""
conditions: []
storedVersions: []
Loading

0 comments on commit b9068bd

Please sign in to comment.