# pf-status-relay-operator **Repository Path**: mirrors_openshift/pf-status-relay-operator ## Basic Information - **Project Name**: pf-status-relay-operator - **Description**: No description available - **Primary Language**: Unknown - **License**: Apache-2.0 - **Default Branch**: main - **Homepage**: None - **GVP Project**: No ## Statistics - **Stars**: 0 - **Forks**: 0 - **Created**: 2024-10-19 - **Last Updated**: 2026-02-14 ## Categories & Tags **Categories**: Uncategorized **Tags**: None ## README # pf-status-relay-operator The pf-status-relay-operator is an Openshift operator that manages the lifecycle of the [pf-status-relay application](https://github.com/openshift/pf-status-relay). ## Description This operator facilitates the deployment of the pf-status-relay application on an Openshift cluster. It provides a custom resource definition (CRD) that allows users to specify the nodes where the application should be deployed, as well as, the interfaces that should be monitored. ``` apiVersion: pfstatusrelay.openshift.io/v1alpha1 kind: PFLACPMonitor metadata: labels: app.kubernetes.io/name: pf-status-relay-operator name: pflacpmonitor-sample spec: interface: - eth0 - eth1 pollingInterval: 1000 nodeSelector: node-role.kubernetes.io/worker: "" hostname: worker-0 ``` Each CRD instance will create a DaemonSet that deploys the pf-status-relay application on the specified nodes. Therefore, to avoid conflicts, the operator won't process CRDs that have common interfaces for a given set of nodes. The CRD is marked as Degraded if the operator detects a conflict. ## Getting Started ### Prerequisites - go version v1.21.0+ - docker version 17.03+. - kubectl version v1.11.3+. - Access to a Kubernetes v1.11.3+ cluster. ### To Deploy on the cluster **Build and push your image to the location specified by `IMG`:** ```sh make docker-build docker-push IMG=/pf-status-relay-operator:tag ``` **NOTE:** This image ought to be published in the personal registry you specified. And it is required to have access to pull the image from the working environment. Make sure you have the proper permission to the registry if the above commands don’t work. **Install the CRDs into the cluster:** ```sh make install ``` **Deploy the Manager to the cluster with the image specified by `IMG`:** ```sh make deploy IMG=/pf-status-relay-operator:tag ``` > **NOTE**: If you encounter RBAC errors, you may need to grant yourself cluster-admin privileges or be logged in as admin. **Create instances of your solution** You can apply the samples (examples) from the config/sample: ```sh kubectl apply -k config/samples/ ``` >**NOTE**: Ensure that the samples has default values to test it out. ### To Uninstall **Delete the instances (CRs) from the cluster:** ```sh kubectl delete -k config/samples/ ``` **Delete the APIs(CRDs) from the cluster:** ```sh make uninstall ``` **UnDeploy the controller from the cluster:** ```sh make undeploy ``` ## Project Distribution Following are the steps to build the installer and distribute this project to users. 1. Build the installer for the image built and published in the registry: ```sh make build-installer IMG=/pf-status-relay-operator:tag ``` NOTE: The makefile target mentioned above generates an 'install.yaml' file in the dist directory. This file contains all the resources built with Kustomize, which are necessary to install this project without its dependencies. 2. Using the installer Users can just run kubectl apply -f to install the project, i.e.: ```sh kubectl apply -f https://raw.githubusercontent.com//pf-status-relay-operator//dist/install.yaml ``` ## Contributing Contributions to this project are welcomed! If you encounter any issues or have suggestions for improvements, please feel free to submit a pull request or open an issue on GitHub. **NOTE:** Run `make help` for more information on all potential `make` targets More information can be found via the [Kubebuilder Documentation](https://book.kubebuilder.io/introduction.html) ## License Copyright 2024. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.