apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T18:48:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-68-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-68.ec2.internal
      uid: a6aacaa8-ffe7-4d42-8bb4-b2c571f607f7
    resourceVersion: "22397"
    uid: e42fc711-9e7b-4644-8598-58f257298c78
  spec:
    sourcePod: network-check-source-6f8b768455-mj4j4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:55:55Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.119228ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:55:55Z"
    - latency: 860.881µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:54:55Z"
    - latency: 923.768µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:53:55Z"
    - latency: 1.115713ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:52:55Z"
    - latency: 1.481797ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:51:55Z"
    - latency: 950.361µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:50:55Z"
    - latency: 950.977µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:49:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T18:48:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-68-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-68.ec2.internal
      uid: a6aacaa8-ffe7-4d42-8bb4-b2c571f607f7
    resourceVersion: "21793"
    uid: 73b82d5b-5488-4fd4-b088-bb346d7d8552
  spec:
    sourcePod: network-check-source-6f8b768455-mj4j4
    targetEndpoint: ad4880f01a9384d4e8e6401861959d4a-34d281b2fa3bbeae.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:54:55Z"
      message: 'load-balancer-api-external: tcp connection to ad4880f01a9384d4e8e6401861959d4a-34d281b2fa3bbeae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.072666ms
      message: 'load-balancer-api-external: tcp connection to ad4880f01a9384d4e8e6401861959d4a-34d281b2fa3bbeae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:54:55Z"
    - latency: 9.359871ms
      message: 'load-balancer-api-external: resolved host name ad4880f01a9384d4e8e6401861959d4a-34d281b2fa3bbeae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:54:55Z"
    - latency: 4.159397ms
      message: 'load-balancer-api-external: tcp connection to ad4880f01a9384d4e8e6401861959d4a-34d281b2fa3bbeae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:53:55Z"
    - latency: 8.950049ms
      message: 'load-balancer-api-external: resolved host name ad4880f01a9384d4e8e6401861959d4a-34d281b2fa3bbeae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:53:55Z"
    - latency: 4.614552ms
      message: 'load-balancer-api-external: tcp connection to ad4880f01a9384d4e8e6401861959d4a-34d281b2fa3bbeae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:52:55Z"
    - latency: 8.686709ms
      message: 'load-balancer-api-external: resolved host name ad4880f01a9384d4e8e6401861959d4a-34d281b2fa3bbeae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:52:55Z"
    - latency: 3.082053ms
      message: 'load-balancer-api-external: tcp connection to ad4880f01a9384d4e8e6401861959d4a-34d281b2fa3bbeae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:51:55Z"
    - latency: 11.293171ms
      message: 'load-balancer-api-external: resolved host name ad4880f01a9384d4e8e6401861959d4a-34d281b2fa3bbeae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:51:55Z"
    - latency: 5.097628ms
      message: 'load-balancer-api-external: tcp connection to ad4880f01a9384d4e8e6401861959d4a-34d281b2fa3bbeae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:50:55Z"
    - latency: 8.645597ms
      message: 'load-balancer-api-external: resolved host name ad4880f01a9384d4e8e6401861959d4a-34d281b2fa3bbeae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:50:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T18:48:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-68-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-68.ec2.internal
      uid: a6aacaa8-ffe7-4d42-8bb4-b2c571f607f7
    resourceVersion: "21792"
    uid: 1f637e9a-bcbb-4f2a-a4e2-62e56a867305
  spec:
    sourcePod: network-check-source-6f8b768455-mj4j4
    targetEndpoint: ad4880f01a9384d4e8e6401861959d4a-34d281b2fa3bbeae.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:54:55Z"
      message: 'load-balancer-api-internal: tcp connection to ad4880f01a9384d4e8e6401861959d4a-34d281b2fa3bbeae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.434758ms
      message: 'load-balancer-api-internal: tcp connection to ad4880f01a9384d4e8e6401861959d4a-34d281b2fa3bbeae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:54:55Z"
    - latency: 9.315605ms
      message: 'load-balancer-api-internal: resolved host name ad4880f01a9384d4e8e6401861959d4a-34d281b2fa3bbeae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:54:55Z"
    - latency: 4.277789ms
      message: 'load-balancer-api-internal: tcp connection to ad4880f01a9384d4e8e6401861959d4a-34d281b2fa3bbeae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:53:55Z"
    - latency: 9.002988ms
      message: 'load-balancer-api-internal: resolved host name ad4880f01a9384d4e8e6401861959d4a-34d281b2fa3bbeae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:53:55Z"
    - latency: 4.636981ms
      message: 'load-balancer-api-internal: tcp connection to ad4880f01a9384d4e8e6401861959d4a-34d281b2fa3bbeae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:52:55Z"
    - latency: 8.598749ms
      message: 'load-balancer-api-internal: resolved host name ad4880f01a9384d4e8e6401861959d4a-34d281b2fa3bbeae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:52:55Z"
    - latency: 4.763549ms
      message: 'load-balancer-api-internal: tcp connection to ad4880f01a9384d4e8e6401861959d4a-34d281b2fa3bbeae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:51:55Z"
    - latency: 11.348471ms
      message: 'load-balancer-api-internal: resolved host name ad4880f01a9384d4e8e6401861959d4a-34d281b2fa3bbeae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:51:55Z"
    - latency: 4.057734ms
      message: 'load-balancer-api-internal: tcp connection to ad4880f01a9384d4e8e6401861959d4a-34d281b2fa3bbeae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:50:55Z"
    - latency: 8.581297ms
      message: 'load-balancer-api-internal: resolved host name ad4880f01a9384d4e8e6401861959d4a-34d281b2fa3bbeae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:50:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T18:48:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-68-to-network-check-target-ip-10-0-134-192
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-68.ec2.internal
      uid: a6aacaa8-ffe7-4d42-8bb4-b2c571f607f7
    resourceVersion: "22395"
    uid: 3de2f105-729f-42a0-be43-88583c7ddf8b
  spec:
    sourcePod: network-check-source-6f8b768455-mj4j4
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:55:55Z"
      message: 'network-check-target-ip-10-0-134-192: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.222898ms
      message: 'network-check-target-ip-10-0-134-192: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:55:55Z"
    - latency: 2.90913ms
      message: 'network-check-target-ip-10-0-134-192: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:54:55Z"
    - latency: 2.269077ms
      message: 'network-check-target-ip-10-0-134-192: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:53:55Z"
    - latency: 2.515266ms
      message: 'network-check-target-ip-10-0-134-192: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:52:55Z"
    - latency: 2.437543ms
      message: 'network-check-target-ip-10-0-134-192: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:51:55Z"
    - latency: 2.206439ms
      message: 'network-check-target-ip-10-0-134-192: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:50:55Z"
    - latency: 2.624348ms
      message: 'network-check-target-ip-10-0-134-192: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:49:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T18:48:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-68-to-network-check-target-ip-10-0-134-68
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-68.ec2.internal
      uid: a6aacaa8-ffe7-4d42-8bb4-b2c571f607f7
    resourceVersion: "22394"
    uid: f3023cd4-9624-49f1-b1ed-7459b56f8070
  spec:
    sourcePod: network-check-source-6f8b768455-mj4j4
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:55:55Z"
      message: 'network-check-target-ip-10-0-134-68: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.42234ms
      message: 'network-check-target-ip-10-0-134-68: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:55:55Z"
    - latency: 922.396µs
      message: 'network-check-target-ip-10-0-134-68: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:54:55Z"
    - latency: 999.75µs
      message: 'network-check-target-ip-10-0-134-68: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:53:55Z"
    - latency: 1.513912ms
      message: 'network-check-target-ip-10-0-134-68: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:52:55Z"
    - latency: 930.878µs
      message: 'network-check-target-ip-10-0-134-68: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:51:55Z"
    - latency: 1.550708ms
      message: 'network-check-target-ip-10-0-134-68: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:50:55Z"
    - latency: 1.678191ms
      message: 'network-check-target-ip-10-0-134-68: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:49:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T18:48:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-68-to-network-check-target-ip-10-0-135-254
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-68.ec2.internal
      uid: a6aacaa8-ffe7-4d42-8bb4-b2c571f607f7
    resourceVersion: "22396"
    uid: 1c69776f-2cc6-4fd7-ba86-7f14818cd08c
  spec:
    sourcePod: network-check-source-6f8b768455-mj4j4
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:55:55Z"
      message: 'network-check-target-ip-10-0-135-254: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.484045ms
      message: 'network-check-target-ip-10-0-135-254: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:55:55Z"
    - latency: 2.241601ms
      message: 'network-check-target-ip-10-0-135-254: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:54:55Z"
    - latency: 2.597529ms
      message: 'network-check-target-ip-10-0-135-254: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:53:55Z"
    - latency: 2.284275ms
      message: 'network-check-target-ip-10-0-135-254: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:52:55Z"
    - latency: 2.271562ms
      message: 'network-check-target-ip-10-0-135-254: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:51:55Z"
    - latency: 2.359822ms
      message: 'network-check-target-ip-10-0-135-254: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:50:55Z"
    - latency: 2.431486ms
      message: 'network-check-target-ip-10-0-135-254: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:49:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T18:48:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-68-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-68.ec2.internal
      uid: a6aacaa8-ffe7-4d42-8bb4-b2c571f607f7
    resourceVersion: "21791"
    uid: 49f925e4-5d01-45a4-879c-d5f8cd996d49
  spec:
    sourcePod: network-check-source-6f8b768455-mj4j4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:54:55Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 839.578µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:54:55Z"
    - latency: 1.845038ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:54:55Z"
    - latency: 1.147295ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:53:55Z"
    - latency: 1.962611ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:53:55Z"
    - latency: 1.124929ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:52:55Z"
    - latency: 2.236824ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:52:55Z"
    - latency: 1.521874ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:51:55Z"
    - latency: 1.801335ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:51:55Z"
    - latency: 1.246303ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:50:55Z"
    - latency: 1.832222ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:50:55Z"
kind: List
metadata:
  resourceVersion: ""