apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T04:44:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-30-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-30.ec2.internal
      uid: dbaab05a-7890-4fc5-8dc7-75e46124cf41
    resourceVersion: "23227"
    uid: 8b6f60af-7a08-4603-a60d-f6745929296d
  spec:
    sourcePod: network-check-source-685456655f-2rmzl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T04:51:16Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.392882ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:51:16Z"
    - latency: 1.005124ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:50:16Z"
    - latency: 912.436µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:49:16Z"
    - latency: 1.187585ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:48:16Z"
    - latency: 1.444186ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:47:16Z"
    - latency: 960.035µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:46:16Z"
    - latency: 1.162363ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:45:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T04:44:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-30-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-30.ec2.internal
      uid: dbaab05a-7890-4fc5-8dc7-75e46124cf41
    resourceVersion: "21982"
    uid: 85165334-0888-4dce-b738-d7307e0f8f76
  spec:
    sourcePod: network-check-source-685456655f-2rmzl
    targetEndpoint: a72eb0d14e340457bb5638e349620a80-3133f476ac2b7568.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T04:50:16Z"
      message: 'load-balancer-api-external: tcp connection to a72eb0d14e340457bb5638e349620a80-3133f476ac2b7568.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.501971ms
      message: 'load-balancer-api-external: tcp connection to a72eb0d14e340457bb5638e349620a80-3133f476ac2b7568.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:50:16Z"
    - latency: 12.533786ms
      message: 'load-balancer-api-external: resolved host name a72eb0d14e340457bb5638e349620a80-3133f476ac2b7568.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T04:50:16Z"
    - latency: 5.297122ms
      message: 'load-balancer-api-external: tcp connection to a72eb0d14e340457bb5638e349620a80-3133f476ac2b7568.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:49:16Z"
    - latency: 7.400991ms
      message: 'load-balancer-api-external: resolved host name a72eb0d14e340457bb5638e349620a80-3133f476ac2b7568.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T04:49:16Z"
    - latency: 4.957806ms
      message: 'load-balancer-api-external: tcp connection to a72eb0d14e340457bb5638e349620a80-3133f476ac2b7568.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:48:16Z"
    - latency: 8.34403ms
      message: 'load-balancer-api-external: resolved host name a72eb0d14e340457bb5638e349620a80-3133f476ac2b7568.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T04:48:16Z"
    - latency: 5.229776ms
      message: 'load-balancer-api-external: tcp connection to a72eb0d14e340457bb5638e349620a80-3133f476ac2b7568.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:47:16Z"
    - latency: 8.59178ms
      message: 'load-balancer-api-external: resolved host name a72eb0d14e340457bb5638e349620a80-3133f476ac2b7568.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T04:47:16Z"
    - latency: 4.043652ms
      message: 'load-balancer-api-external: tcp connection to a72eb0d14e340457bb5638e349620a80-3133f476ac2b7568.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:46:16Z"
    - latency: 8.426877ms
      message: 'load-balancer-api-external: resolved host name a72eb0d14e340457bb5638e349620a80-3133f476ac2b7568.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T04:46:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T04:44:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-30-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-30.ec2.internal
      uid: dbaab05a-7890-4fc5-8dc7-75e46124cf41
    resourceVersion: "21981"
    uid: 6f69b511-29c1-44b0-8e93-fa7d863e944c
  spec:
    sourcePod: network-check-source-685456655f-2rmzl
    targetEndpoint: a72eb0d14e340457bb5638e349620a80-3133f476ac2b7568.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T04:50:16Z"
      message: 'load-balancer-api-internal: tcp connection to a72eb0d14e340457bb5638e349620a80-3133f476ac2b7568.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.014928ms
      message: 'load-balancer-api-internal: tcp connection to a72eb0d14e340457bb5638e349620a80-3133f476ac2b7568.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:50:16Z"
    - latency: 12.449163ms
      message: 'load-balancer-api-internal: resolved host name a72eb0d14e340457bb5638e349620a80-3133f476ac2b7568.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T04:50:16Z"
    - latency: 4.332396ms
      message: 'load-balancer-api-internal: tcp connection to a72eb0d14e340457bb5638e349620a80-3133f476ac2b7568.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:49:16Z"
    - latency: 7.305832ms
      message: 'load-balancer-api-internal: resolved host name a72eb0d14e340457bb5638e349620a80-3133f476ac2b7568.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T04:49:16Z"
    - latency: 3.568645ms
      message: 'load-balancer-api-internal: tcp connection to a72eb0d14e340457bb5638e349620a80-3133f476ac2b7568.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:48:16Z"
    - latency: 8.255288ms
      message: 'load-balancer-api-internal: resolved host name a72eb0d14e340457bb5638e349620a80-3133f476ac2b7568.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T04:48:16Z"
    - latency: 5.225469ms
      message: 'load-balancer-api-internal: tcp connection to a72eb0d14e340457bb5638e349620a80-3133f476ac2b7568.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:47:16Z"
    - latency: 8.499717ms
      message: 'load-balancer-api-internal: resolved host name a72eb0d14e340457bb5638e349620a80-3133f476ac2b7568.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T04:47:16Z"
    - latency: 5.746828ms
      message: 'load-balancer-api-internal: tcp connection to a72eb0d14e340457bb5638e349620a80-3133f476ac2b7568.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:46:16Z"
    - latency: 8.34503ms
      message: 'load-balancer-api-internal: resolved host name a72eb0d14e340457bb5638e349620a80-3133f476ac2b7568.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T04:46:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T04:44:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-30-to-network-check-target-ip-10-0-131-132
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-30.ec2.internal
      uid: dbaab05a-7890-4fc5-8dc7-75e46124cf41
    resourceVersion: "23226"
    uid: 9b079564-1626-4b50-aaa0-04e782aef8b3
  spec:
    sourcePod: network-check-source-685456655f-2rmzl
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T04:51:16Z"
      message: 'network-check-target-ip-10-0-131-132: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.555915ms
      message: 'network-check-target-ip-10-0-131-132: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:51:16Z"
    - latency: 2.453122ms
      message: 'network-check-target-ip-10-0-131-132: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:50:16Z"
    - latency: 2.359981ms
      message: 'network-check-target-ip-10-0-131-132: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:49:16Z"
    - latency: 2.345154ms
      message: 'network-check-target-ip-10-0-131-132: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:48:16Z"
    - latency: 2.346415ms
      message: 'network-check-target-ip-10-0-131-132: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:47:16Z"
    - latency: 2.325371ms
      message: 'network-check-target-ip-10-0-131-132: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:46:16Z"
    - latency: 2.679773ms
      message: 'network-check-target-ip-10-0-131-132: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:45:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T04:44:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-30-to-network-check-target-ip-10-0-134-30
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-30.ec2.internal
      uid: dbaab05a-7890-4fc5-8dc7-75e46124cf41
    resourceVersion: "23224"
    uid: ef1f78ed-9e1d-4e3d-a707-f6fa824a70b2
  spec:
    sourcePod: network-check-source-685456655f-2rmzl
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T04:51:16Z"
      message: 'network-check-target-ip-10-0-134-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.66713ms
      message: 'network-check-target-ip-10-0-134-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:51:16Z"
    - latency: 1.440335ms
      message: 'network-check-target-ip-10-0-134-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:50:16Z"
    - latency: 1.422577ms
      message: 'network-check-target-ip-10-0-134-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:49:16Z"
    - latency: 974.874µs
      message: 'network-check-target-ip-10-0-134-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:48:16Z"
    - latency: 1.369048ms
      message: 'network-check-target-ip-10-0-134-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:47:16Z"
    - latency: 944.445µs
      message: 'network-check-target-ip-10-0-134-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:46:16Z"
    - latency: 1.9263ms
      message: 'network-check-target-ip-10-0-134-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:45:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T04:44:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-30-to-network-check-target-ip-10-0-136-230
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-30.ec2.internal
      uid: dbaab05a-7890-4fc5-8dc7-75e46124cf41
    resourceVersion: "23225"
    uid: df947962-26c9-4c12-8f7a-87be2aecd887
  spec:
    sourcePod: network-check-source-685456655f-2rmzl
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T04:51:16Z"
      message: 'network-check-target-ip-10-0-136-230: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.623995ms
      message: 'network-check-target-ip-10-0-136-230: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:51:16Z"
    - latency: 2.257735ms
      message: 'network-check-target-ip-10-0-136-230: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:50:16Z"
    - latency: 2.614387ms
      message: 'network-check-target-ip-10-0-136-230: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:49:16Z"
    - latency: 2.180591ms
      message: 'network-check-target-ip-10-0-136-230: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:48:16Z"
    - latency: 2.477048ms
      message: 'network-check-target-ip-10-0-136-230: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:47:16Z"
    - latency: 2.303052ms
      message: 'network-check-target-ip-10-0-136-230: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:46:16Z"
    - latency: 2.665468ms
      message: 'network-check-target-ip-10-0-136-230: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:45:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T04:44:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-30-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-30.ec2.internal
      uid: dbaab05a-7890-4fc5-8dc7-75e46124cf41
    resourceVersion: "21980"
    uid: 32147ad5-aaff-42a9-923f-f7dca021a3df
  spec:
    sourcePod: network-check-source-685456655f-2rmzl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T04:50:16Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.531167ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:50:16Z"
    - latency: 1.837946ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T04:50:16Z"
    - latency: 914.075µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:49:16Z"
    - latency: 1.86283ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T04:49:16Z"
    - latency: 1.006017ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:48:16Z"
    - latency: 1.861739ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T04:48:16Z"
    - latency: 1.43747ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:47:16Z"
    - latency: 1.860128ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T04:47:16Z"
    - latency: 762.382µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:46:16Z"
    - latency: 1.906857ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T04:46:16Z"
kind: List
metadata:
  resourceVersion: ""