newrelic/kubernetes-operator Docker 镜像 - 轩辕镜像

New Relic Kubernetes Operator

![Testing]([] ![Security Scan]([] ![Go Report Card]([] ![GoDoc]([] ![License]([] ![CLA assistant]([] ![Release]([***]

![Docker Stars]([] ![Docker Pulls]([] ![Docker Size]([] ![Docker Version]([]

• Overview
• Quick Start
• Using the Operator to Provision Resources
  • Create a New Relic alert policy
  • Create a New Relic NRQL alert condition
• Development

Overview

The newrelic-kubernetes-operator is a Kubernetes Operator that facilitates management of New Relic resources from within your Kubernetes configuration. Managing New Relic resources via custom Kubernetes objects can be done the same way you manage built-in Kubernetes objects.

Currently the operator supports managing the following resources:

• Alert Policies
• NRQL Alert Conditions.
• Alert Conditions for APM, Browser and mobile

Quick Start

Note: These quick start instructions do not require you to clone the repo.

Running Kubernetes in a Docker container locally with kind

1. Install docker, kubectl, kustomize, and kind

   bash
   brew cask install docker
   brew install kubernetes-cli kustomize kind
   

2. Create a test cluster with kind

   bash
   kind create cluster --name newrelic
   kubectl cluster-info
   

3. Install cert-manager

   bash
   kubectl apply --validate=false -f [***]
   

   Note: This takes a minute or two to finish so wait a minute before going on to the next step.

   You can also confirm it's running with the command kubectl rollout status deployment -n cert-manager cert-manager-webhook

4. Install the operator in the test cluster.

   bash
   kustomize build github.com/newrelic/newrelic-kubernetes-operator/configs/default | kubectl apply -f -
   

   Note: This will install operator on whatever kubernetes cluster kubectl is configured to use.

Using a custom container

If you want to deploy the operator in a custom container you can override the image name with a kustomize.yaml file.

1. Create a new kustomize.yaml file

   yaml
   apiVersion: kustomize.config.k8s.io/v1beta1
   kind: Kustomization
   namespace: newrelic-kubernetes-operator-system
   resources:
     - github.com/newrelic/newrelic-kubernetes-operator/configs/default
   images:
     - name: newrelic/k8s-operator:snapshot
       newName: <CUSTOM_IMAGE>
       newTag: <CUSTOM_TAG>
   

2. The apply the file with:

   bash
   kustomize build . | kubectl apply -f -
   

Provision New Relic resources with the operator

Once you've completed the Quick Start section, you can start provisioning New Relic resources with our New Relic Kubernetes objects.

Create a New Relic alert policy with NRQL alert conditions

1. We'll be using the following example policy configuration file. You will need to update the api_key field with your New Relic personal API key.
   

   examples/example_policy.yaml

   yaml
   apiVersion: nr.k8s.newrelic.com/v1
   kind: Policy
   metadata:
     name: my-policy
   spec:
     # Add your API key here
     api_key: <your New Relic personal API key>
     name: k8s created policy
     incident_preference: "PER_POLICY"
     region: "us"
     conditions:
       - spec:
           nrql:
             query: "SELECT count(*) FROM Transactions"
             since_value: "10"
           enabled: true
           terms:
             - threshold: "75.0"
               time_function: "all"
               duration: "5"
               priority: "critical"
               operator: "above"
           name: "K8s generated alert condition"
       - spec:
           type: "apm_app_metric"
           enabled: true
           metric: "apdex"
           condition_scope: application
           entities:
             - "5950260"
           terms:
             - threshold: "0.9"
               time_function: "all"
               duration: "30"
               priority: "critical"
               operator: "above"
           name: "K8s generated apm alert condition 2"
   

   Once you've added your API key, we can apply it your local cluster.

   bash
   kubectl apply -f examples/example_policy.yaml
   

   Note: You can also use a Kubernetes secret for providing your API key. We've provided an example secret configuration file in case you want to use this method. You'll need to replace api_key with api_key_secret.

2. See your configured policies with the following command.

   bash
   kubectl describe policies.nr.k8s.newrelic.com
   

   Note: You should also see the newly created policy within your New Relic account.

The operator will create and update alert policies and NRQL alert conditions as needed by applying your configuration files with kubectl apply -f <filename>

Create a NRQL alert condition and add it to an existing alert policy

1. We'll be using the following example NRQL alert condition configuration file. You will need to update the api_key field with your New Relic personal API key.
   

   examples/example_nrql_alert_condition.yaml

   yaml
   apiVersion: nr.k8s.newrelic.com/v1
   kind: NrqlAlertCondition
   metadata:
     name: my-alert-condition
   spec:
     # Add your API key here
     api_key: <your New Relic personal API key>
     name: "K8s generated alert condition"
     nrql:
       # Note: This is just an example.
       # You'll want to use a query with parameters that are
       # more specific to the needs for targeting associated
       # kubernetes objects.
       query: "SELECT count(*) FROM Transactions"
       since_value: "10"
     enabled: true
     terms:
       - threshold: "75.0"
         time_function: "all"
         duration: "5"
         priority: "critical"
         operator: "above"
     existing_policy_id: 26458245 # Note: must match an existing policy in your account
     region: "us"
   

Uninstall the operator

The Operator can be removed with the reverse of installation, namely building the kubernetes resource files with kustomize and running kubectl delete

bash
kustomize build github.com/newrelic/newrelic-kubernetes-operator/configs/default | kubectl delete -f -

Development

This section should get you set up properly for doing development on the operator.

Requirements

• Go v1.13+
• Docker (with Kubernetes enabled)
• kubectl
• kustomize
• kubebuilder

Code

1. Clone the repo

   bash
   git clone ***:newrelic/newrelic-kubernetes-operator.git
   

2. Install kubebuilder following the instructions for your operating system. This installation will also get etcd and kube-apiserver which are needed for the tests.
   

   Note: Do not install kubebuilder with brew. Homebrew's kubebuilder package will not provide all the necessary dependencies for running the tests.

3. Run the test suite, which uses the Ginkgo testing framework. Using the make targets is the quickest way to get started with testing.

   • Running tests with make

     bash
     make test              # runs all tests
     make test-unit         # only runs unit tests
     make test-integration  # only runs integration tests
     

   • Linting the codebase

     bash
     make lint
     

4. Perform the steps from the Quick Start section, which walk through the initial required setup and get you going with your first kubectl apply of the operator configuration.

5. Confirm your configuration was deployed to your local Kubernetes cluster (the one that we created with kind).
   

   • Show your namespaces. You should see newrelic-kubernetes-operator-system in the list of namespaces.

     bash
     kubectl get namespaces
     

   • Show the nodes within the newrelic-kubernetes-operator-system namespace.

     bash
     kubectl get nodes -n newrelic-kubernetes-operator-system
     

     You should see something similar to the following output:

     NAME                     STATUS   ROLES    AGE    VERSION
     newrelic-control-plane   Ready    master   163m   v1.18.2
     

6. Next steps:

   • Create a New Relic alert policy
   • Create a New Relic NRQL alert condition

Helpful commands

bash
# Describe the currently configured policies.
kubectl describe policies.nr.k8s.newrelic.com

# Describe the currently configured alert conditions.
kubectl describe nrqlalertconditions.nr.k8s.newrelic.com

# Get the node being used for the newrelic operator.
kubectl get nodes -n newrelic-kubernetes-operator-system

# Describe the node being used for the newrelic operator.
kubectl describe node <your-node-name>

# Tail logs of the operator's manager container (useful during development).
# Use the `describe node` command above to locate your manager controller.
kubectl logs -f -n newrelic-kubernetes-operator-system -c manager newrelic-kubernetes-operator-controller-manager-<hash from>