apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T20:04:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-66-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-66.ec2.internal
      uid: 2ec91835-eab8-481d-b2f4-a3f12ed0365f
    resourceVersion: "10854"
    uid: 6cf8b3c1-8bd1-47c1-a0a6-efe4d3fa56e0
  spec:
    sourcePod: network-check-source-989f8b8dc-8jbzq
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:11:51Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 907.081µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:11:51Z"
    - latency: 1.28674ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:10:51Z"
    - latency: 1.297515ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:09:51Z"
    - latency: 880.303µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:08:51Z"
    - latency: 844.765µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:07:51Z"
    - latency: 759.371µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:06:51Z"
    - latency: 1.02245ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T20:04:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-66-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-66.ec2.internal
      uid: 2ec91835-eab8-481d-b2f4-a3f12ed0365f
    resourceVersion: "10738"
    uid: 19c5358c-f7ca-4b41-a0b7-f09fe605885e
  spec:
    sourcePod: network-check-source-989f8b8dc-8jbzq
    targetEndpoint: aac89cf985817439e86fc6cc4218dada-4dd0bdd8f7edcfa0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:10:51Z"
      message: 'load-balancer-api-external: tcp connection to aac89cf985817439e86fc6cc4218dada-4dd0bdd8f7edcfa0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.936093ms
      message: 'load-balancer-api-external: tcp connection to aac89cf985817439e86fc6cc4218dada-4dd0bdd8f7edcfa0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:10:51Z"
    - latency: 7.671443ms
      message: 'load-balancer-api-external: resolved host name aac89cf985817439e86fc6cc4218dada-4dd0bdd8f7edcfa0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:10:51Z"
    - latency: 4.10494ms
      message: 'load-balancer-api-external: tcp connection to aac89cf985817439e86fc6cc4218dada-4dd0bdd8f7edcfa0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:09:51Z"
    - latency: 8.678558ms
      message: 'load-balancer-api-external: resolved host name aac89cf985817439e86fc6cc4218dada-4dd0bdd8f7edcfa0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:09:51Z"
    - latency: 4.474473ms
      message: 'load-balancer-api-external: tcp connection to aac89cf985817439e86fc6cc4218dada-4dd0bdd8f7edcfa0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:08:51Z"
    - latency: 7.785898ms
      message: 'load-balancer-api-external: resolved host name aac89cf985817439e86fc6cc4218dada-4dd0bdd8f7edcfa0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:08:51Z"
    - latency: 3.151433ms
      message: 'load-balancer-api-external: tcp connection to aac89cf985817439e86fc6cc4218dada-4dd0bdd8f7edcfa0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:07:51Z"
    - latency: 13.218094ms
      message: 'load-balancer-api-external: resolved host name aac89cf985817439e86fc6cc4218dada-4dd0bdd8f7edcfa0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:07:51Z"
    - latency: 5.40672ms
      message: 'load-balancer-api-external: tcp connection to aac89cf985817439e86fc6cc4218dada-4dd0bdd8f7edcfa0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:06:51Z"
    - latency: 8.383401ms
      message: 'load-balancer-api-external: resolved host name aac89cf985817439e86fc6cc4218dada-4dd0bdd8f7edcfa0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:06:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T20:04:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-66-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-66.ec2.internal
      uid: 2ec91835-eab8-481d-b2f4-a3f12ed0365f
    resourceVersion: "10739"
    uid: 16d42c9b-bfe7-454c-9c86-9cadbcb03e53
  spec:
    sourcePod: network-check-source-989f8b8dc-8jbzq
    targetEndpoint: aac89cf985817439e86fc6cc4218dada-4dd0bdd8f7edcfa0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:10:51Z"
      message: 'load-balancer-api-internal: tcp connection to aac89cf985817439e86fc6cc4218dada-4dd0bdd8f7edcfa0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.759008ms
      message: 'load-balancer-api-internal: tcp connection to aac89cf985817439e86fc6cc4218dada-4dd0bdd8f7edcfa0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:10:51Z"
    - latency: 7.628709ms
      message: 'load-balancer-api-internal: resolved host name aac89cf985817439e86fc6cc4218dada-4dd0bdd8f7edcfa0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:10:51Z"
    - latency: 4.220898ms
      message: 'load-balancer-api-internal: tcp connection to aac89cf985817439e86fc6cc4218dada-4dd0bdd8f7edcfa0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:09:51Z"
    - latency: 8.625738ms
      message: 'load-balancer-api-internal: resolved host name aac89cf985817439e86fc6cc4218dada-4dd0bdd8f7edcfa0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:09:51Z"
    - latency: 4.112869ms
      message: 'load-balancer-api-internal: tcp connection to aac89cf985817439e86fc6cc4218dada-4dd0bdd8f7edcfa0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:08:51Z"
    - latency: 7.759632ms
      message: 'load-balancer-api-internal: resolved host name aac89cf985817439e86fc6cc4218dada-4dd0bdd8f7edcfa0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:08:51Z"
    - latency: 4.248595ms
      message: 'load-balancer-api-internal: tcp connection to aac89cf985817439e86fc6cc4218dada-4dd0bdd8f7edcfa0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:07:51Z"
    - latency: 13.098208ms
      message: 'load-balancer-api-internal: resolved host name aac89cf985817439e86fc6cc4218dada-4dd0bdd8f7edcfa0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:07:51Z"
    - latency: 5.418951ms
      message: 'load-balancer-api-internal: tcp connection to aac89cf985817439e86fc6cc4218dada-4dd0bdd8f7edcfa0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:06:51Z"
    - latency: 8.348445ms
      message: 'load-balancer-api-internal: resolved host name aac89cf985817439e86fc6cc4218dada-4dd0bdd8f7edcfa0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:06:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T20:04:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-66-to-network-check-target-ip-10-0-137-86
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-66.ec2.internal
      uid: 2ec91835-eab8-481d-b2f4-a3f12ed0365f
    resourceVersion: "10853"
    uid: 2e8824d7-1e9c-4a2c-9f19-f61564246990
  spec:
    sourcePod: network-check-source-989f8b8dc-8jbzq
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:11:51Z"
      message: 'network-check-target-ip-10-0-137-86: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.241339ms
      message: 'network-check-target-ip-10-0-137-86: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:11:51Z"
    - latency: 2.463883ms
      message: 'network-check-target-ip-10-0-137-86: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:10:51Z"
    - latency: 2.244299ms
      message: 'network-check-target-ip-10-0-137-86: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:09:51Z"
    - latency: 2.301723ms
      message: 'network-check-target-ip-10-0-137-86: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:08:51Z"
    - latency: 2.227889ms
      message: 'network-check-target-ip-10-0-137-86: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:07:51Z"
    - latency: 2.284955ms
      message: 'network-check-target-ip-10-0-137-86: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:06:51Z"
    - latency: 2.665042ms
      message: 'network-check-target-ip-10-0-137-86: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T20:04:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-66-to-network-check-target-ip-10-0-139-66
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-66.ec2.internal
      uid: 2ec91835-eab8-481d-b2f4-a3f12ed0365f
    resourceVersion: "10851"
    uid: 71f97ecf-c8d8-464e-a898-f46c24de3e98
  spec:
    sourcePod: network-check-source-989f8b8dc-8jbzq
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:11:51Z"
      message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 875.245µs
      message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:11:51Z"
    - latency: 879.833µs
      message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:10:51Z"
    - latency: 1.364488ms
      message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:09:51Z"
    - latency: 905.114µs
      message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:08:51Z"
    - latency: 939.46µs
      message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:07:51Z"
    - latency: 1.250193ms
      message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:06:51Z"
    - latency: 1.823994ms
      message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T20:04:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-66-to-network-check-target-ip-10-0-140-196
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-66.ec2.internal
      uid: 2ec91835-eab8-481d-b2f4-a3f12ed0365f
    resourceVersion: "10852"
    uid: ebe64add-1bce-40d3-90f3-ce89f952d68e
  spec:
    sourcePod: network-check-source-989f8b8dc-8jbzq
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:11:51Z"
      message: 'network-check-target-ip-10-0-140-196: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.307378ms
      message: 'network-check-target-ip-10-0-140-196: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:11:51Z"
    - latency: 2.54595ms
      message: 'network-check-target-ip-10-0-140-196: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:10:51Z"
    - latency: 2.462755ms
      message: 'network-check-target-ip-10-0-140-196: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:09:51Z"
    - latency: 2.288041ms
      message: 'network-check-target-ip-10-0-140-196: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:08:51Z"
    - latency: 2.502996ms
      message: 'network-check-target-ip-10-0-140-196: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:07:51Z"
    - latency: 2.313779ms
      message: 'network-check-target-ip-10-0-140-196: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:06:51Z"
    - latency: 2.570901ms
      message: 'network-check-target-ip-10-0-140-196: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T20:04:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-66-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-66.ec2.internal
      uid: 2ec91835-eab8-481d-b2f4-a3f12ed0365f
    resourceVersion: "10737"
    uid: d5724da3-2254-4868-89cf-85bf935906d7
  spec:
    sourcePod: network-check-source-989f8b8dc-8jbzq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:10:51Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 772.715µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:10:51Z"
    - latency: 1.662076ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:10:51Z"
    - latency: 1.199614ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:09:51Z"
    - latency: 1.644335ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:09:51Z"
    - latency: 869.839µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:08:51Z"
    - latency: 1.591026ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:08:51Z"
    - latency: 879.353µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:07:51Z"
    - latency: 6.5247ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:07:51Z"
    - latency: 927.589µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:06:51Z"
    - latency: 2.38592ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:06:51Z"
kind: List
metadata:
  resourceVersion: ""