config-kourier created 2021-08-30 18:59:58, version 6788 

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
apiVersion: v1
data:
  _example: '################################

    #                              #

    #    EXAMPLE CONFIGURATION     #

    #                              #

    ################################


    # This block is not actually functional configuration,

    # but serves to illustrate the available configuration

    # options and document them in a way that is accessible

    # to users that `kubectl edit` this config map.

    #

    # These sample configuration options may be copied out of

    # this example block and unindented to be in the data block

    # to actually change the configuration.


    # Specifies whether requests reaching the Kourier gateway

    # in the context of services should be logged. Readiness

    # probes etc. must be configured via the bootstrap config.

    enable-service-access-logging: "true"

    '
kind: ConfigMap
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: '{"apiVersion":"v1","data":{"_example":"################################\n#                              #\n#    EXAMPLE
      CONFIGURATION     #\n#                              #\n################################\n\n#
      This block is not actually functional configuration,\n# but serves to illustrate
      the available configuration\n# options and document them in a way that is accessible\n#
      to users that `kubectl edit` this config map.\n#\n# These sample configuration
      options may be copied out of\n# this example block and unindented to be in the
      data block\n# to actually change the configuration.\n\n# Specifies whether requests
      reaching the Kourier gateway\n# in the context of services should be logged.
      Readiness\n# probes etc. must be configured via the bootstrap config.\nenable-service-access-logging:
      \"true\"\n"},"kind":"ConfigMap","metadata":{"labels":{"networking.knative.dev/ingress-provider":"kourier","serving.knative.dev/release":"v0.24.0"},"name":"config-kourier","namespace":"knative-serving","ownerReferences":[{"apiVersion":"operator.knative.dev/v1alpha1","blockOwnerDeletion":true,"controller":true,"kind":"KnativeServing","name":"knative-serving","uid":"5162f181-a47b-4465-a388-ee8a99ad290e"}]}}

      '
  creationTimestamp: '2021-08-30T18:59:58Z'
  labels:
    networking.knative.dev/ingress-provider: kourier
    serving.knative.dev/release: v0.24.0
  managedFields:
  - apiVersion: v1
    fieldsType: FieldsV1
    fieldsV1:
      f:data:
        .: {}
        f:_example: {}
      f:metadata:
        f:annotations:
          .: {}
          f:kubectl.kubernetes.io/last-applied-configuration: {}
        f:labels:
          .: {}
          f:networking.knative.dev/ingress-provider: {}
          f:serving.knative.dev/release: {}
        f:ownerReferences:
          .: {}
          k:{"uid":"5162f181-a47b-4465-a388-ee8a99ad290e"}:
            .: {}
            f:apiVersion: {}
            f:blockOwnerDeletion: {}
            f:controller: {}
            f:kind: {}
            f:name: {}
            f:uid: {}
    manager: manifestival
    operation: Update
    time: '2021-08-30T19:00:12Z'
  name: config-kourier
  namespace: knative-serving
  ownerReferences:
  - apiVersion: operator.knative.dev/v1alpha1
    blockOwnerDeletion: true
    controller: true
    kind: KnativeServing
    name: knative-serving
    uid: 5162f181-a47b-4465-a388-ee8a99ad290e
  resourceVersion: '6788'
  uid: b3b7f77a-9408-40f6-8af7-32680a7b1d3e