Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-9410

[doc]missing apiversion when creating secret from sample yaml

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • 2.13.1 GA
    • Documentation
    • None
    • 2
    • False
    • None
    • False
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Moderate

      In the document https://access.redhat.com/documentation/en-us/red_hat_3scale_api_management/2.13/html/installing_3scale/install-threescale-on-openshift-guide#amazon_s3_secret the secret yaml example, if we paste it directly, cannot be applied successfuly because it miss the apiVersion at the header.

      kind: Secret
metadata:
  creationTimestamp: null
  name: aws-auth
stringData:
  AWS_ACCESS_KEY_ID: 123456
  AWS_SECRET_ACCESS_KEY: 98765544
  AWS_BUCKET: mybucket.example.com
  AWS_REGION: eu-west-1
type: Opaque

      should be:

      apiVersion: v1
kind: Secret
metadata:
  creationTimestamp: null
  name: aws-auth
stringData:
  AWS_ACCESS_KEY_ID: 123456
  AWS_SECRET_ACCESS_KEY: 98765544
  AWS_BUCKET: mybucket.example.com
  AWS_REGION: eu-west-1
type: Opaque

      Without the proper apiVersion, one will face error

      [root@bastion-rhel8 3scale]# oc apply -f secret.yaml
Error from server (NotFound): error when creating "secret.yaml": the server could not find the requested resource

      previous version of doc has the same issue.

              rhn-support-lcavalle Lluis Cavalle
              rhn-support-bihu Bin Hu
              Lluis Cavalle Lluis Cavalle
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: