apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-13T20:19:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-99-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-99.ec2.internal
      uid: 1e8bcf53-24b3-4eda-8df5-598858b06738
    resourceVersion: "24111"
    uid: 8f176648-819c-484f-a25e-36fd1449fb0b
  spec:
    sourcePod: network-check-source-6f8b768455-f8hfw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-13T20:26:27Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 916.131µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:26:27Z"
    - latency: 1.489511ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:25:27Z"
    - latency: 1.180839ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:24:27Z"
    - latency: 1.087714ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:23:27Z"
    - latency: 1.07429ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:22:27Z"
    - latency: 1.419776ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:21:27Z"
    - latency: 1.047674ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:20:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-13T20:19:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-99-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-99.ec2.internal
      uid: 1e8bcf53-24b3-4eda-8df5-598858b06738
    resourceVersion: "27616"
    uid: 0e98162c-bfd8-4409-99c6-d851354bf0f8
  spec:
    sourcePod: network-check-source-6f8b768455-f8hfw
    targetEndpoint: a7bb2da58fb334e67ac9d3fb9afe59eb-362f36e474377f56.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-13T20:25:27Z"
      message: 'load-balancer-api-external: tcp connection to a7bb2da58fb334e67ac9d3fb9afe59eb-362f36e474377f56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.484342ms
      message: 'load-balancer-api-external: tcp connection to a7bb2da58fb334e67ac9d3fb9afe59eb-362f36e474377f56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:31:27Z"
    - latency: 9.516961ms
      message: 'load-balancer-api-external: resolved host name a7bb2da58fb334e67ac9d3fb9afe59eb-362f36e474377f56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T20:31:27Z"
    - latency: 4.4923ms
      message: 'load-balancer-api-external: tcp connection to a7bb2da58fb334e67ac9d3fb9afe59eb-362f36e474377f56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:30:27Z"
    - latency: 15.815086ms
      message: 'load-balancer-api-external: resolved host name a7bb2da58fb334e67ac9d3fb9afe59eb-362f36e474377f56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T20:30:27Z"
    - latency: 3.985605ms
      message: 'load-balancer-api-external: tcp connection to a7bb2da58fb334e67ac9d3fb9afe59eb-362f36e474377f56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:29:27Z"
    - latency: 15.378881ms
      message: 'load-balancer-api-external: resolved host name a7bb2da58fb334e67ac9d3fb9afe59eb-362f36e474377f56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T20:29:27Z"
    - latency: 5.874339ms
      message: 'load-balancer-api-external: tcp connection to a7bb2da58fb334e67ac9d3fb9afe59eb-362f36e474377f56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:28:27Z"
    - latency: 7.930102ms
      message: 'load-balancer-api-external: resolved host name a7bb2da58fb334e67ac9d3fb9afe59eb-362f36e474377f56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T20:28:27Z"
    - latency: 5.363414ms
      message: 'load-balancer-api-external: tcp connection to a7bb2da58fb334e67ac9d3fb9afe59eb-362f36e474377f56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:27:27Z"
    - latency: 9.706183ms
      message: 'load-balancer-api-external: resolved host name a7bb2da58fb334e67ac9d3fb9afe59eb-362f36e474377f56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T20:27:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-13T20:19:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-99-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-99.ec2.internal
      uid: 1e8bcf53-24b3-4eda-8df5-598858b06738
    resourceVersion: "27615"
    uid: 1c586b91-839a-49b1-96f2-8ee4ed8f06ed
  spec:
    sourcePod: network-check-source-6f8b768455-f8hfw
    targetEndpoint: a7bb2da58fb334e67ac9d3fb9afe59eb-362f36e474377f56.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-13T20:25:27Z"
      message: 'load-balancer-api-internal: tcp connection to a7bb2da58fb334e67ac9d3fb9afe59eb-362f36e474377f56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.476779ms
      message: 'load-balancer-api-internal: tcp connection to a7bb2da58fb334e67ac9d3fb9afe59eb-362f36e474377f56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:31:27Z"
    - latency: 9.469024ms
      message: 'load-balancer-api-internal: resolved host name a7bb2da58fb334e67ac9d3fb9afe59eb-362f36e474377f56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T20:31:27Z"
    - latency: 4.456737ms
      message: 'load-balancer-api-internal: tcp connection to a7bb2da58fb334e67ac9d3fb9afe59eb-362f36e474377f56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:30:27Z"
    - latency: 15.747118ms
      message: 'load-balancer-api-internal: resolved host name a7bb2da58fb334e67ac9d3fb9afe59eb-362f36e474377f56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T20:30:27Z"
    - latency: 3.97792ms
      message: 'load-balancer-api-internal: tcp connection to a7bb2da58fb334e67ac9d3fb9afe59eb-362f36e474377f56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:29:27Z"
    - latency: 15.341354ms
      message: 'load-balancer-api-internal: resolved host name a7bb2da58fb334e67ac9d3fb9afe59eb-362f36e474377f56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T20:29:27Z"
    - latency: 5.755136ms
      message: 'load-balancer-api-internal: tcp connection to a7bb2da58fb334e67ac9d3fb9afe59eb-362f36e474377f56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:28:27Z"
    - latency: 7.890252ms
      message: 'load-balancer-api-internal: resolved host name a7bb2da58fb334e67ac9d3fb9afe59eb-362f36e474377f56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T20:28:27Z"
    - latency: 5.393997ms
      message: 'load-balancer-api-internal: tcp connection to a7bb2da58fb334e67ac9d3fb9afe59eb-362f36e474377f56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:27:27Z"
    - latency: 9.655441ms
      message: 'load-balancer-api-internal: resolved host name a7bb2da58fb334e67ac9d3fb9afe59eb-362f36e474377f56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T20:27:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-13T20:19:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-99-to-network-check-target-ip-10-0-134-99
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-99.ec2.internal
      uid: 1e8bcf53-24b3-4eda-8df5-598858b06738
    resourceVersion: "24108"
    uid: a9a62a3d-7fb5-4819-8dc5-44c215674efe
  spec:
    sourcePod: network-check-source-6f8b768455-f8hfw
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-13T20:26:27Z"
      message: 'network-check-target-ip-10-0-134-99: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.108096ms
      message: 'network-check-target-ip-10-0-134-99: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:26:27Z"
    - latency: 1.726814ms
      message: 'network-check-target-ip-10-0-134-99: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:25:27Z"
    - latency: 840.881µs
      message: 'network-check-target-ip-10-0-134-99: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:24:27Z"
    - latency: 932.037µs
      message: 'network-check-target-ip-10-0-134-99: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:23:27Z"
    - latency: 766.276µs
      message: 'network-check-target-ip-10-0-134-99: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:22:27Z"
    - latency: 1.13023ms
      message: 'network-check-target-ip-10-0-134-99: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:21:27Z"
    - latency: 1.356405ms
      message: 'network-check-target-ip-10-0-134-99: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:20:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-13T20:19:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-99-to-network-check-target-ip-10-0-140-25
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-99.ec2.internal
      uid: 1e8bcf53-24b3-4eda-8df5-598858b06738
    resourceVersion: "24110"
    uid: 57bc582f-0469-4492-84b7-af3543435e53
  spec:
    sourcePod: network-check-source-6f8b768455-f8hfw
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-13T20:26:27Z"
      message: 'network-check-target-ip-10-0-140-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.300288ms
      message: 'network-check-target-ip-10-0-140-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:26:27Z"
    - latency: 2.295077ms
      message: 'network-check-target-ip-10-0-140-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:25:27Z"
    - latency: 1.940945ms
      message: 'network-check-target-ip-10-0-140-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:24:27Z"
    - latency: 1.889449ms
      message: 'network-check-target-ip-10-0-140-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:23:27Z"
    - latency: 2.100285ms
      message: 'network-check-target-ip-10-0-140-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:22:27Z"
    - latency: 2.192265ms
      message: 'network-check-target-ip-10-0-140-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:21:27Z"
    - latency: 1.957846ms
      message: 'network-check-target-ip-10-0-140-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:20:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-13T20:19:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-99-to-network-check-target-ip-10-0-141-59
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-99.ec2.internal
      uid: 1e8bcf53-24b3-4eda-8df5-598858b06738
    resourceVersion: "24109"
    uid: ed8d9b16-e0d7-4573-a1c4-a89afe85abc7
  spec:
    sourcePod: network-check-source-6f8b768455-f8hfw
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-13T20:26:27Z"
      message: 'network-check-target-ip-10-0-141-59: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.394235ms
      message: 'network-check-target-ip-10-0-141-59: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:26:27Z"
    - latency: 1.942503ms
      message: 'network-check-target-ip-10-0-141-59: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:25:27Z"
    - latency: 2.165986ms
      message: 'network-check-target-ip-10-0-141-59: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:24:27Z"
    - latency: 1.958237ms
      message: 'network-check-target-ip-10-0-141-59: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:23:27Z"
    - latency: 2.319996ms
      message: 'network-check-target-ip-10-0-141-59: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:22:27Z"
    - latency: 2.456078ms
      message: 'network-check-target-ip-10-0-141-59: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:21:27Z"
    - latency: 1.973716ms
      message: 'network-check-target-ip-10-0-141-59: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:20:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-13T20:19:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-99-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-99.ec2.internal
      uid: 1e8bcf53-24b3-4eda-8df5-598858b06738
    resourceVersion: "27614"
    uid: 4144235d-83e2-4a6c-9d42-3d794605d4e1
  spec:
    sourcePod: network-check-source-6f8b768455-f8hfw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-13T20:25:27Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.336219ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:31:27Z"
    - latency: 1.682628ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T20:31:27Z"
    - latency: 764.913µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:30:27Z"
    - latency: 1.836541ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T20:30:27Z"
    - latency: 957.758µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:29:27Z"
    - latency: 1.670103ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T20:29:27Z"
    - latency: 10.773782ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:28:27Z"
    - latency: 2.08236ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T20:28:27Z"
    - latency: 992.521µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T20:27:27Z"
    - latency: 1.801729ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T20:27:27Z"
kind: List
metadata:
  resourceVersion: ""