apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T02:50:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-172-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-172.ec2.internal
      uid: 6b952286-a403-481e-84f2-59d4187e9eac
    resourceVersion: "15688"
    uid: 55509766-cf72-4f05-8fac-a3bd3becc8e8
  spec:
    sourcePod: network-check-source-6f8b768455-xkqlk
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T02:57:35Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 918.414µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:57:35Z"
    - latency: 1.385319ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:56:35Z"
    - latency: 1.260476ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:55:35Z"
    - latency: 1.095362ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:54:35Z"
    - latency: 955.364µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:53:35Z"
    - latency: 845.934µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:52:35Z"
    - latency: 1.106234ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:51:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T02:50:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-172-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-172.ec2.internal
      uid: 6b952286-a403-481e-84f2-59d4187e9eac
    resourceVersion: "15241"
    uid: 00300fb7-3081-44d2-8e6a-4c8699fe2a07
  spec:
    sourcePod: network-check-source-6f8b768455-xkqlk
    targetEndpoint: af3ccc5826f1b4f6b8e3b96344531a87-2ed7375e6bf8e79c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T02:56:35Z"
      message: 'load-balancer-api-external: tcp connection to af3ccc5826f1b4f6b8e3b96344531a87-2ed7375e6bf8e79c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.487236ms
      message: 'load-balancer-api-external: tcp connection to af3ccc5826f1b4f6b8e3b96344531a87-2ed7375e6bf8e79c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:56:35Z"
    - latency: 6.042727ms
      message: 'load-balancer-api-external: resolved host name af3ccc5826f1b4f6b8e3b96344531a87-2ed7375e6bf8e79c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T02:56:35Z"
    - latency: 4.563021ms
      message: 'load-balancer-api-external: tcp connection to af3ccc5826f1b4f6b8e3b96344531a87-2ed7375e6bf8e79c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:55:35Z"
    - latency: 8.548305ms
      message: 'load-balancer-api-external: resolved host name af3ccc5826f1b4f6b8e3b96344531a87-2ed7375e6bf8e79c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T02:55:35Z"
    - latency: 3.980846ms
      message: 'load-balancer-api-external: tcp connection to af3ccc5826f1b4f6b8e3b96344531a87-2ed7375e6bf8e79c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:54:35Z"
    - latency: 7.268027ms
      message: 'load-balancer-api-external: resolved host name af3ccc5826f1b4f6b8e3b96344531a87-2ed7375e6bf8e79c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T02:54:35Z"
    - latency: 4.831794ms
      message: 'load-balancer-api-external: tcp connection to af3ccc5826f1b4f6b8e3b96344531a87-2ed7375e6bf8e79c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:53:35Z"
    - latency: 8.803148ms
      message: 'load-balancer-api-external: resolved host name af3ccc5826f1b4f6b8e3b96344531a87-2ed7375e6bf8e79c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T02:53:35Z"
    - latency: 4.347382ms
      message: 'load-balancer-api-external: tcp connection to af3ccc5826f1b4f6b8e3b96344531a87-2ed7375e6bf8e79c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:52:35Z"
    - latency: 8.71103ms
      message: 'load-balancer-api-external: resolved host name af3ccc5826f1b4f6b8e3b96344531a87-2ed7375e6bf8e79c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T02:52:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T02:50:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-172-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-172.ec2.internal
      uid: 6b952286-a403-481e-84f2-59d4187e9eac
    resourceVersion: "15240"
    uid: 585814e7-e091-4056-a530-43641ca27956
  spec:
    sourcePod: network-check-source-6f8b768455-xkqlk
    targetEndpoint: af3ccc5826f1b4f6b8e3b96344531a87-2ed7375e6bf8e79c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T02:56:35Z"
      message: 'load-balancer-api-internal: tcp connection to af3ccc5826f1b4f6b8e3b96344531a87-2ed7375e6bf8e79c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.281ms
      message: 'load-balancer-api-internal: tcp connection to af3ccc5826f1b4f6b8e3b96344531a87-2ed7375e6bf8e79c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:56:35Z"
    - latency: 6.106475ms
      message: 'load-balancer-api-internal: resolved host name af3ccc5826f1b4f6b8e3b96344531a87-2ed7375e6bf8e79c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T02:56:35Z"
    - latency: 4.541834ms
      message: 'load-balancer-api-internal: tcp connection to af3ccc5826f1b4f6b8e3b96344531a87-2ed7375e6bf8e79c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:55:35Z"
    - latency: 8.591157ms
      message: 'load-balancer-api-internal: resolved host name af3ccc5826f1b4f6b8e3b96344531a87-2ed7375e6bf8e79c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T02:55:35Z"
    - latency: 3.851889ms
      message: 'load-balancer-api-internal: tcp connection to af3ccc5826f1b4f6b8e3b96344531a87-2ed7375e6bf8e79c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:54:35Z"
    - latency: 7.308969ms
      message: 'load-balancer-api-internal: resolved host name af3ccc5826f1b4f6b8e3b96344531a87-2ed7375e6bf8e79c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T02:54:35Z"
    - latency: 4.875178ms
      message: 'load-balancer-api-internal: tcp connection to af3ccc5826f1b4f6b8e3b96344531a87-2ed7375e6bf8e79c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:53:35Z"
    - latency: 8.822295ms
      message: 'load-balancer-api-internal: resolved host name af3ccc5826f1b4f6b8e3b96344531a87-2ed7375e6bf8e79c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T02:53:35Z"
    - latency: 3.947555ms
      message: 'load-balancer-api-internal: tcp connection to af3ccc5826f1b4f6b8e3b96344531a87-2ed7375e6bf8e79c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:52:35Z"
    - latency: 8.759496ms
      message: 'load-balancer-api-internal: resolved host name af3ccc5826f1b4f6b8e3b96344531a87-2ed7375e6bf8e79c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T02:52:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T02:50:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-172-to-network-check-target-ip-10-0-133-172
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-172.ec2.internal
      uid: 6b952286-a403-481e-84f2-59d4187e9eac
    resourceVersion: "15685"
    uid: 43ed113d-9aaa-4f73-9404-0938c7f26919
  spec:
    sourcePod: network-check-source-6f8b768455-xkqlk
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T02:57:35Z"
      message: 'network-check-target-ip-10-0-133-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 915.021µs
      message: 'network-check-target-ip-10-0-133-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:57:35Z"
    - latency: 1.174112ms
      message: 'network-check-target-ip-10-0-133-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:56:35Z"
    - latency: 1.073052ms
      message: 'network-check-target-ip-10-0-133-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:55:35Z"
    - latency: 948.942µs
      message: 'network-check-target-ip-10-0-133-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:54:35Z"
    - latency: 1.053545ms
      message: 'network-check-target-ip-10-0-133-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:53:35Z"
    - latency: 988.916µs
      message: 'network-check-target-ip-10-0-133-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:52:35Z"
    - latency: 2.124019ms
      message: 'network-check-target-ip-10-0-133-172: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:51:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T02:50:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-172-to-network-check-target-ip-10-0-135-174
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-172.ec2.internal
      uid: 6b952286-a403-481e-84f2-59d4187e9eac
    resourceVersion: "15687"
    uid: b5cfb65d-07ac-48fd-a205-67ef554b65e2
  spec:
    sourcePod: network-check-source-6f8b768455-xkqlk
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T02:57:35Z"
      message: 'network-check-target-ip-10-0-135-174: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.985516ms
      message: 'network-check-target-ip-10-0-135-174: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:57:35Z"
    - latency: 2.253307ms
      message: 'network-check-target-ip-10-0-135-174: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:56:35Z"
    - latency: 2.425218ms
      message: 'network-check-target-ip-10-0-135-174: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:55:35Z"
    - latency: 2.398288ms
      message: 'network-check-target-ip-10-0-135-174: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:54:35Z"
    - latency: 2.542617ms
      message: 'network-check-target-ip-10-0-135-174: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:53:35Z"
    - latency: 2.116966ms
      message: 'network-check-target-ip-10-0-135-174: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:52:35Z"
    - latency: 2.524496ms
      message: 'network-check-target-ip-10-0-135-174: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:51:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T02:50:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-172-to-network-check-target-ip-10-0-136-12
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-172.ec2.internal
      uid: 6b952286-a403-481e-84f2-59d4187e9eac
    resourceVersion: "15686"
    uid: 015101c0-203b-4f26-86fc-78c82f33064f
  spec:
    sourcePod: network-check-source-6f8b768455-xkqlk
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T02:57:35Z"
      message: 'network-check-target-ip-10-0-136-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.082121ms
      message: 'network-check-target-ip-10-0-136-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:57:35Z"
    - latency: 2.047506ms
      message: 'network-check-target-ip-10-0-136-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:56:35Z"
    - latency: 2.047238ms
      message: 'network-check-target-ip-10-0-136-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:55:35Z"
    - latency: 2.382499ms
      message: 'network-check-target-ip-10-0-136-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:54:35Z"
    - latency: 2.41688ms
      message: 'network-check-target-ip-10-0-136-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:53:35Z"
    - latency: 2.26322ms
      message: 'network-check-target-ip-10-0-136-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:52:35Z"
    - latency: 2.946233ms
      message: 'network-check-target-ip-10-0-136-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:51:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T02:50:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-172-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-172.ec2.internal
      uid: 6b952286-a403-481e-84f2-59d4187e9eac
    resourceVersion: "15239"
    uid: 3e69ad1c-e2ea-4956-8e44-67c41166c681
  spec:
    sourcePod: network-check-source-6f8b768455-xkqlk
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T02:56:35Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.335947ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:56:35Z"
    - latency: 1.63611ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T02:56:35Z"
    - latency: 984.935µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:55:35Z"
    - latency: 1.856366ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T02:55:35Z"
    - latency: 941.57µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:54:35Z"
    - latency: 1.79904ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T02:54:35Z"
    - latency: 834.561µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:53:35Z"
    - latency: 1.69764ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T02:53:35Z"
    - latency: 1.001783ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:52:35Z"
    - latency: 1.822053ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T02:52:35Z"
kind: List
metadata:
  resourceVersion: ""