Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tKb6B-009cpe-Tk for pgsql-admin@arkaria.postgresql.org; Mon, 09 Dec 2024 10:34:43 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tKb69-0077Wb-Bh for pgsql-admin@arkaria.postgresql.org; Mon, 09 Dec 2024 10:34:42 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tKb69-0077WT-06 for pgsql-admin@lists.postgresql.org; Mon, 09 Dec 2024 10:34:42 +0000 Received: from mail-qv1-xf30.google.com ([2607:f8b0:4864:20::f30]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tKb63-001rx6-GK for pgsql-admin@lists.postgresql.org; Mon, 09 Dec 2024 10:34:41 +0000 Received: by mail-qv1-xf30.google.com with SMTP id 6a1803df08f44-6d8f65ef5abso14792306d6.3 for ; Mon, 09 Dec 2024 02:34:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1733740474; x=1734345274; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=jY5MAFfTPuj3XdbijI3nVR2AJ4F6yu8ERc0gFkqjNAE=; b=HS6Xh6q52EYYbD1ZmrQ4lQmyKYR5qGd3+7KoRuqGxRdaYnU1L+dsrjxNs0OZbN3lPQ agfZ0Ck5QZ5UPV3w0z7dYMxGyIuCyYRqdWFzlX+2pgPguJJNicNhjz4GsTf3zu3qBmIV 00FzGvbPypn+Ms3pfZ/WgM3n9cUEnrJRnBzt5FTC8zOMrD5XGfMTVyXu6puzNV8dUjZK ydG2W1PzuPkhmdccLjzL7TfIB4sL5jk/OnizJ1C3DLirrwaPK8sZLZjBAjBtxjI97zeJ WjAtJVxT2+opYx5bWwjzpvxpV3SBEwTjlY1bYZDWetcbnGD/HwKZ3WqLcQY5f0lPpGa6 lqLA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1733740474; x=1734345274; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=jY5MAFfTPuj3XdbijI3nVR2AJ4F6yu8ERc0gFkqjNAE=; b=j8khDa+g1le3kiQtqtHhkbvJ12WfyBiRDQ9TIlBi+DS/9uyoYq5+uNJzdR3zo52qIm nRHNCma4xlUweXmyp26Xinj3mhgi1n07y7DRn7yAq4eIBgSdA0yccemQrrvRap6ZuIPq UgPUrq7tQqPttORk8FCsz/14jk6p2bIENDEr4Zs4O0EQ5YOtxtvgAH+hHYKnRsoqBqf7 Br8pJIZWgByKRdPKm9VAmTZEoPkRGys9k3S7fijvYxpaovfX0ceGXaXythpzb7gQlDYQ 2lnW2deWuGSjkaR+S+cx6Witg968hyKZCl0ByuPANsinMQJcB+CPORhAGNY1UibJEAMh MGdA== X-Gm-Message-State: AOJu0YxHeyMX23LtzTkf3WwImIBP1IEz4mCtWp49p7zzuKTz9rQ5u5Q6 OUe3d/DngwKJxcOi7qbzKKzt6SYlYcwg9gYRUcdMuNjwORKj7OGjg7ZJtEXeRN2IgZBvX9+Hy/C AxQXRZqNEFkjKYGT9Nwp6OZXIYQHjuw== X-Gm-Gg: ASbGnctWkwlEK53uuJC7xhinnDH0YyuYC8Nhfnsr58uTcDEqsBbN0XjSWYcsaHK/Oaj 3m6sxIFfsREeJWbCoqitVMeu6j8eF14kJ X-Google-Smtp-Source: AGHT+IERRnT3rGl1UyghUUS2gdMed0LdrdArqDf3dEG/le4Z3J3qzwjFZJfGXArZk5uaIfYq7TJ2xoZwPXJU5XkBrw4= X-Received: by 2002:ad4:596c:0:b0:6d8:a967:8387 with SMTP id 6a1803df08f44-6d8e70d674fmr167624416d6.1.1733740474267; Mon, 09 Dec 2024 02:34:34 -0800 (PST) MIME-Version: 1.0 From: AjithKumar Kannan Date: Mon, 9 Dec 2024 16:04:23 +0530 Message-ID: Subject: Does kubernetes v1.30 support the zalando operator v1.9.0? To: pgsql-admin@lists.postgresql.org Content-Type: multipart/alternative; boundary="0000000000001a04f40628d3e979" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000001a04f40628d3e979 Content-Type: text/plain; charset="UTF-8" Hi All, Good afternoon, We are currently using K8s v1.24 with zalando operator v1.9.0 and planning to upgrade K8s to v1.30. Anyone using K8s v1.30 with zalando operator 1.9.0? Please advice Regards, Ajith --0000000000001a04f40628d3e979 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi All,

Good= afternoon,

We are curre= ntly using K8s v1.24 with zalando operator v1.9.0 and planning to upgrade K= 8s to v1.30.

Anyone usin= g K8s v1.30 with zalando operator 1.9.0? Please advice

Regards,
Ajith
<= /div> --0000000000001a04f40628d3e979--