diff --git a/api/openapi-spec/swagger.json b/api/openapi-spec/swagger.json
index 3be69d41e88..d62f58bc189 100644
--- a/api/openapi-spec/swagger.json
+++ b/api/openapi-spec/swagger.json
@@ -34956,11 +34956,8 @@
       "description": "Data contains the secret data. Each key must be a valid DNS_SUBDOMAIN or leading dot followed by valid DNS_SUBDOMAIN. The serialized form of the secret data is a base64 encoded string, representing the arbitrary (possibly non-string) data value here. Described in https://tools.ietf.org/html/rfc4648#section-4",
       "type": "object",
       "additionalProperties": {
-       "type": "array",
-       "items": {
-        "type": "integer",
-        "format": "byte"
-       }
+       "type": "string",
+       "format": "byte"
       }
      },
      "metadata": {
diff --git a/federation/apis/openapi-spec/swagger.json b/federation/apis/openapi-spec/swagger.json
index acf10e55ddd..108ad12232a 100644
--- a/federation/apis/openapi-spec/swagger.json
+++ b/federation/apis/openapi-spec/swagger.json
@@ -9273,11 +9273,8 @@
       "description": "Data contains the secret data. Each key must be a valid DNS_SUBDOMAIN or leading dot followed by valid DNS_SUBDOMAIN. The serialized form of the secret data is a base64 encoded string, representing the arbitrary (possibly non-string) data value here. Described in https://tools.ietf.org/html/rfc4648#section-4",
       "type": "object",
       "additionalProperties": {
-       "type": "array",
-       "items": {
-        "type": "integer",
-        "format": "byte"
-       }
+       "type": "string",
+       "format": "byte"
       }
      },
      "metadata": {