apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T01:45:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-136-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-136.us-west-2.compute.internal
      uid: 5d3546d6-7cdc-464e-9f22-61c4e8196e06
    resourceVersion: "18693"
    uid: e5915659-4a79-48de-b814-630ca82e39b2
  spec:
    sourcePod: network-check-source-6f78d59f99-z284f
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T01:52:14Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.162368ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:52:14Z"
    - latency: 870.815µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:51:14Z"
    - latency: 841.57µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:50:14Z"
    - latency: 1.359443ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:49:14Z"
    - latency: 1.642531ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:48:14Z"
    - latency: 1.592931ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:47:14Z"
    - latency: 1.404706ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:46:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T01:45:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-136-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-136.us-west-2.compute.internal
      uid: 5d3546d6-7cdc-464e-9f22-61c4e8196e06
    resourceVersion: "20958"
    uid: 255eb161-fc03-4fbb-ba71-08836c2257b6
  spec:
    sourcePod: network-check-source-6f78d59f99-z284f
    targetEndpoint: a0647fa545e4d4687bfff40f1365d88a-d315861558085486.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T01:51:14Z"
      message: 'load-balancer-api-external: tcp connection to a0647fa545e4d4687bfff40f1365d88a-d315861558085486.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 56.331639ms
      message: 'load-balancer-api-external: tcp connection to a0647fa545e4d4687bfff40f1365d88a-d315861558085486.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:57:14Z"
    - latency: 9.725459ms
      message: 'load-balancer-api-external: resolved host name a0647fa545e4d4687bfff40f1365d88a-d315861558085486.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T01:57:14Z"
    - latency: 56.349889ms
      message: 'load-balancer-api-external: tcp connection to a0647fa545e4d4687bfff40f1365d88a-d315861558085486.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:56:14Z"
    - latency: 6.980465ms
      message: 'load-balancer-api-external: resolved host name a0647fa545e4d4687bfff40f1365d88a-d315861558085486.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T01:56:14Z"
    - latency: 55.326148ms
      message: 'load-balancer-api-external: tcp connection to a0647fa545e4d4687bfff40f1365d88a-d315861558085486.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:55:14Z"
    - latency: 7.433427ms
      message: 'load-balancer-api-external: resolved host name a0647fa545e4d4687bfff40f1365d88a-d315861558085486.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T01:55:14Z"
    - latency: 55.555144ms
      message: 'load-balancer-api-external: tcp connection to a0647fa545e4d4687bfff40f1365d88a-d315861558085486.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:54:14Z"
    - latency: 7.791964ms
      message: 'load-balancer-api-external: resolved host name a0647fa545e4d4687bfff40f1365d88a-d315861558085486.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T01:54:14Z"
    - latency: 61.046346ms
      message: 'load-balancer-api-external: tcp connection to a0647fa545e4d4687bfff40f1365d88a-d315861558085486.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:53:14Z"
    - latency: 8.021954ms
      message: 'load-balancer-api-external: resolved host name a0647fa545e4d4687bfff40f1365d88a-d315861558085486.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T01:53:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T01:45:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-136-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-136.us-west-2.compute.internal
      uid: 5d3546d6-7cdc-464e-9f22-61c4e8196e06
    resourceVersion: "20957"
    uid: 35876937-07ff-4cec-8a87-f16d319cbcd7
  spec:
    sourcePod: network-check-source-6f78d59f99-z284f
    targetEndpoint: a0647fa545e4d4687bfff40f1365d88a-d315861558085486.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T01:51:14Z"
      message: 'load-balancer-api-internal: tcp connection to a0647fa545e4d4687bfff40f1365d88a-d315861558085486.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 51.153196ms
      message: 'load-balancer-api-internal: tcp connection to a0647fa545e4d4687bfff40f1365d88a-d315861558085486.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:57:14Z"
    - latency: 9.769056ms
      message: 'load-balancer-api-internal: resolved host name a0647fa545e4d4687bfff40f1365d88a-d315861558085486.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T01:57:14Z"
    - latency: 56.364284ms
      message: 'load-balancer-api-internal: tcp connection to a0647fa545e4d4687bfff40f1365d88a-d315861558085486.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:56:14Z"
    - latency: 7.060144ms
      message: 'load-balancer-api-internal: resolved host name a0647fa545e4d4687bfff40f1365d88a-d315861558085486.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T01:56:14Z"
    - latency: 51.024645ms
      message: 'load-balancer-api-internal: tcp connection to a0647fa545e4d4687bfff40f1365d88a-d315861558085486.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:55:14Z"
    - latency: 7.382297ms
      message: 'load-balancer-api-internal: resolved host name a0647fa545e4d4687bfff40f1365d88a-d315861558085486.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T01:55:14Z"
    - latency: 50.624438ms
      message: 'load-balancer-api-internal: tcp connection to a0647fa545e4d4687bfff40f1365d88a-d315861558085486.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:54:14Z"
    - latency: 7.853977ms
      message: 'load-balancer-api-internal: resolved host name a0647fa545e4d4687bfff40f1365d88a-d315861558085486.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T01:54:14Z"
    - latency: 52.110175ms
      message: 'load-balancer-api-internal: tcp connection to a0647fa545e4d4687bfff40f1365d88a-d315861558085486.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:53:14Z"
    - latency: 8.048479ms
      message: 'load-balancer-api-internal: resolved host name a0647fa545e4d4687bfff40f1365d88a-d315861558085486.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T01:53:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T01:45:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-136-to-network-check-target-ip-10-0-129-136
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-136.us-west-2.compute.internal
      uid: 5d3546d6-7cdc-464e-9f22-61c4e8196e06
    resourceVersion: "18688"
    uid: 301e4ea8-05ac-49b2-acd3-c11b312497dc
  spec:
    sourcePod: network-check-source-6f78d59f99-z284f
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T01:52:14Z"
      message: 'network-check-target-ip-10-0-129-136: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 832.6µs
      message: 'network-check-target-ip-10-0-129-136: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:52:14Z"
    - latency: 867.589µs
      message: 'network-check-target-ip-10-0-129-136: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:51:14Z"
    - latency: 935.712µs
      message: 'network-check-target-ip-10-0-129-136: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:50:14Z"
    - latency: 1.550321ms
      message: 'network-check-target-ip-10-0-129-136: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:49:14Z"
    - latency: 841.179µs
      message: 'network-check-target-ip-10-0-129-136: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:48:14Z"
    - latency: 771.561µs
      message: 'network-check-target-ip-10-0-129-136: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:47:14Z"
    - latency: 1.349996ms
      message: 'network-check-target-ip-10-0-129-136: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:46:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T01:45:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-136-to-network-check-target-ip-10-0-131-149
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-136.us-west-2.compute.internal
      uid: 5d3546d6-7cdc-464e-9f22-61c4e8196e06
    resourceVersion: "18689"
    uid: cdfc78e2-1034-4cac-a3f7-47e3f8e8a1ec
  spec:
    sourcePod: network-check-source-6f78d59f99-z284f
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T01:52:14Z"
      message: 'network-check-target-ip-10-0-131-149: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.8363ms
      message: 'network-check-target-ip-10-0-131-149: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:52:14Z"
    - latency: 1.769274ms
      message: 'network-check-target-ip-10-0-131-149: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:51:14Z"
    - latency: 1.969608ms
      message: 'network-check-target-ip-10-0-131-149: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:50:14Z"
    - latency: 2.162025ms
      message: 'network-check-target-ip-10-0-131-149: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:49:14Z"
    - latency: 1.907109ms
      message: 'network-check-target-ip-10-0-131-149: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:48:14Z"
    - latency: 1.740688ms
      message: 'network-check-target-ip-10-0-131-149: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:47:14Z"
    - latency: 1.90601ms
      message: 'network-check-target-ip-10-0-131-149: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:46:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T01:45:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-136-to-network-check-target-ip-10-0-138-33
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-136.us-west-2.compute.internal
      uid: 5d3546d6-7cdc-464e-9f22-61c4e8196e06
    resourceVersion: "18690"
    uid: b4944a05-710b-4f36-beb9-916a6f39ee12
  spec:
    sourcePod: network-check-source-6f78d59f99-z284f
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T01:52:14Z"
      message: 'network-check-target-ip-10-0-138-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.091233ms
      message: 'network-check-target-ip-10-0-138-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:52:14Z"
    - latency: 2.168721ms
      message: 'network-check-target-ip-10-0-138-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:51:14Z"
    - latency: 2.307845ms
      message: 'network-check-target-ip-10-0-138-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:50:14Z"
    - latency: 2.156529ms
      message: 'network-check-target-ip-10-0-138-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:49:14Z"
    - latency: 2.414443ms
      message: 'network-check-target-ip-10-0-138-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:48:14Z"
    - latency: 2.902569ms
      message: 'network-check-target-ip-10-0-138-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:47:14Z"
    - latency: 2.697187ms
      message: 'network-check-target-ip-10-0-138-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:46:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T01:45:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-136-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-136.us-west-2.compute.internal
      uid: 5d3546d6-7cdc-464e-9f22-61c4e8196e06
    resourceVersion: "20954"
    uid: 35bb9a57-daa7-426e-ab61-4562a1ff57c1
  spec:
    sourcePod: network-check-source-6f78d59f99-z284f
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T01:51:14Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.165259ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:57:14Z"
    - latency: 2.395488ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T01:57:14Z"
    - latency: 893.362µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:56:14Z"
    - latency: 1.826864ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T01:56:14Z"
    - latency: 839.353µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:55:14Z"
    - latency: 1.732108ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T01:55:14Z"
    - latency: 845.15µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:54:14Z"
    - latency: 1.795298ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T01:54:14Z"
    - latency: 1.042441ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:53:14Z"
    - latency: 2.142747ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T01:53:14Z"
kind: List
metadata:
  resourceVersion: ""