anchor.diff:  
   You can create multiple Management Contexts, each targeting a specific environment and defined in a specific organization of a management API instance.
   
  -A Management Context can authenticate to your management API instance by using either basic authentication or a bearer token.
  +A Management Context can authenticate to your management API instance by using either basic authentication or a bearer token. Authentication credentials may either be added inline in the Management Context definition or referenced from a Kubernetes secret.
   
   NOTE: If both credentials and a bearer token are defined in your custom resource, the bearer token will take precedence.
   
   == Examples
   
  -The custom resource in the example below refers to a Management API instance exposed at `+https://gravitee-api.acme.com+`, and targets the `dev` environment of the `acme` organization, with the `admin` account, using basic auth:
  +The custom resource in the example below refers to a Management API instance exposed at `+https://gravitee-api.acme.com+`, and targets the `dev` environment of the `acme` organization, with the `admin` account, using basic authentication credentials defined in a Kubernetes secret:
  +
  +Creating a secret to store the credentials:
  +
  +[source,yaml]
  +----
  +kubectl create secret generic management-context-credentials \
  +  --from-literal=username=admin \
  +  --from-literal=password=admin \
  +  --namespace graviteeio
  +----
  +
  +Defining a Management Context referencing the secret:
   
   [,yaml]
   ----
  
positive.code: kind: ManagementContext
  metadata:
    name: apim-example-context
  spec:
    baseUrl: https://gravitee-api.acme.com
    environmentId: dev
    organizationId: acme
    auth:
      credentials:
        username: admin
        password: admin
  ----
  
  NOTE: To target another environment on the same API instance, add another Management Context targeting that environment.
  
  The example below uses a `bearerToken` to authenticate the requests. Note that the token must have been generated beforehand for the admin account:
  
  
negative.code:   auth:
      bearerToken: xxxx-yyyy-zzzz
  ----
  
  Alternatively, here is how to use a Kubernetes secret to store the token:
  
  [source,yaml]
  ----
  kubectl create secret generic management-context-credentials \
    --from-literal=bearerToken=xxxx-yyyy-zzzz \
    --namespace graviteeio
  ----
  
  [,yaml]
  ----
  apiVersion: gravitee.io/v1alpha1
  kind: ManagementContext
  metadata:
    name: apim-example-context
  spec:
    baseUrl: https://gravitee-api.acme.com
    environmentId: staging
    organizationId: acme
    auth:
      secretRef:
        name: management-context-credentials
  ----
  