{"id":33433,"date":"2024-06-08T14:28:01","date_gmt":"2024-06-08T12:28:01","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/?p=33433"},"modified":"2024-06-08T14:28:01","modified_gmt":"2024-06-08T12:28:01","slug":"cloudnativepg-bootstrapping-an-empty-cluster","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/cloudnativepg-bootstrapping-an-empty-cluster\/","title":{"rendered":"CloudnativePG &#8211; Bootstrapping an empty cluster"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">In the <a href=\"https:\/\/www.dbi-services.com\/blog\/cloudnativepg-on-minicube-on-opensuse-leap-micro-6\/\" target=\"_blank\" rel=\"noreferrer noopener\">last post<\/a> we&#8217;ve created a very simple three node PostgreSQL cluster using <a href=\"https:\/\/cloudnative-pg.io\/\">CloudNativePG<\/a> and this was really easy to do. While this is great to get started quickly, you usually want to have more control on how PostgreSQL is initialized and configured. In this post we&#8217;ll look at bootstrapping the cluster and what options you have for controlling it, when you want to start with an empty cluster.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">What we got in the last post was mostly a default configuration. Lets start from scratch by deleting the existing cluster:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: bash; highlight: [1,4,6,8]; title: ; notranslate\" title=\"\">\nminicube@micro-minicube:~&gt; kubectl get cluster -A\nNAMESPACE   NAME              AGE   INSTANCES   READY   STATUS                     PRIMARY\ndefault     cluster-example   26h   3           3       Cluster in healthy state   cluster-example-1\nminicube@micro-minicube:~&gt; kubectl delete cluster cluster-example\ncluster.postgresql.cnpg.io &quot;cluster-example&quot; deleted\nminicube@micro-minicube:~&gt; kubectl get cluster -A\nNo resources found\nminicube@micro-minicube:~&gt; kubectl get pods\nNo resources found in default namespace.\nminicube@micro-minicube:~&gt;\n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\">Instead of using the minimal configuration from the last post, we&#8217;ll now use this one to describe our cluster:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: bash; highlight: [1]; title: ; notranslate\" title=\"\">\nminicube@micro-minicube:~&gt; cat pg.yaml\napiVersion: postgresql.cnpg.io\/v1\nkind: Cluster\nmetadata:\n  name: my-pg-cluster\nspec:\n  instances: 3\n\n  bootstrap:\n    initdb:\n      database: db1\n      owner: db1\n      dataChecksums: true\n      walSegmentSize: 32\n  storage:\n    size: 1Gi\n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\">This is what changed (all under the &#8220;initdb&#8221; section):<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The name of the cluster<\/li>\n\n\n\n<li>We want a new database &#8220;db1&#8221; to be created and this database should be owned by a new user called &#8220;db1&#8221;<\/li>\n\n\n\n<li>We want data checksum to be enabled<\/li>\n\n\n\n<li>Finally we want to change the WAL segment size from the default of 16MB to 32MB<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Once we apply this, we of course get the same picture as before for the pods and the services:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: bash; highlight: [1,3]; title: ; notranslate\" title=\"\">\nminicube@micro-minicube:~&gt; kubectl apply -f pg.yaml\ncluster.postgresql.cnpg.io\/my-pg-cluster created\nminicube@micro-minicube:~&gt; kubectl get pods\nNAME              READY   STATUS    RESTARTS   AGE\nmy-pg-cluster-1   1\/1     Running   0          119s\nmy-pg-cluster-2   1\/1     Running   0          97s\nmy-pg-cluster-3   1\/1     Running   0          78s\n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\">Lets take one of these pods, start a shell and check what was created:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: bash; highlight: [1,3,7]; title: ; notranslate\" title=\"\">\nminicube@micro-minicube:~&gt; kubectl exec my-pg-cluster-2 -i -t -- \/bin\/bash\nDefaulted container &quot;postgres&quot; out of: postgres, bootstrap-controller (init)\npostgres@my-pg-cluster-2:\/$ psql\npsql (16.2 (Debian 16.2-1.pgdg110+2))\nType &quot;help&quot; for help.\n\npostgres=# \\l\n                                                  List of databases\n   Name    |  Owner   | Encoding | Locale Provider | Collate | Ctype | ICU Locale | ICU Rules |   Access privileges\n-----------+----------+----------+-----------------+---------+-------+------------+-----------+-----------------------\n db1       | db1      | UTF8     | libc            | C       | C     |            |           |\n postgres  | postgres | UTF8     | libc            | C       | C     |            |           |\n template0 | postgres | UTF8     | libc            | C       | C     |            |           | =c\/postgres          +\n           |          |          |                 |         |       |            |           | postgres=CTc\/postgres\n template1 | postgres | UTF8     | libc            | C       | C     |            |           | =c\/postgres          +\n           |          |          |                 |         |       |            |           | postgres=CTc\/postgres\n(4 rows)\n\npostgres=#\n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\">We got the database and the database is owned by the new user. What we also can see is, the we got &#8220;C&#8221; for the &#8220;Collate&#8221; and &#8220;Ctype&#8221;. This is probably not what you want, so you also need to change this in the initdb section of the cluster definition:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; highlight: [1]; title: ; notranslate\" title=\"\">\nminicube@micro-minicube:~&amp;gt; cat pg.yaml\napiVersion: postgresql.cnpg.io\/v1\nkind: Cluster\nmetadata:\n  name: my-pg-cluster\nspec:\n  instances: 3\n\n  bootstrap:\n    initdb:\n      database: db1\n      owner: db1\n      dataChecksums: true\n      walSegmentSize: 32\n      localeCollate: &#039;en_US.utf8&#039;\n      localeCType: &#039;en_US.utf8&#039;\n  storage:\n    size: 1Gi\n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\">Destroy, re-create and check again:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: bash; highlight: [1,3,5,10,12,16]; title: ; notranslate\" title=\"\">\nminicube@micro-minicube:~&gt; kubectl delete -f pg.yaml\ncluster.postgresql.cnpg.io &quot;my-pg-cluster&quot; deleted\nminicube@micro-minicube:~&gt; kubectl apply -f pg.yaml\ncluster.postgresql.cnpg.io\/my-pg-cluster created\nminicube@micro-minicube:~&gt; kubectl get pods\nNAME              READY   STATUS    RESTARTS   AGE\nmy-pg-cluster-1   1\/1     Running   0          55m\nmy-pg-cluster-2   1\/1     Running   0          54m\nmy-pg-cluster-3   1\/1     Running   0          54m\nminicube@micro-minicube:~&gt; kubectl exec my-pg-cluster-1 -i -t -- \/bin\/bash\nDefaulted container &quot;postgres&quot; out of: postgres, bootstrap-controller (init)\npostgres@my-pg-cluster-1:\/$ psql\npsql (16.2 (Debian 16.2-1.pgdg110+2))\nType &quot;help&quot; for help.\n\npostgres=# \\l\n                                                      List of databases\n   Name    |  Owner   | Encoding | Locale Provider |  Collate   |   Ctype    | ICU Locale | ICU Rules |   Access privileges   \n-----------+----------+----------+-----------------+------------+------------+------------+-----------+-----------------------\n db1       | db1      | UTF8     | libc            | en_US.utf8 | en_US.utf8 |            |           | \n postgres  | postgres | UTF8     | libc            | en_US.utf8 | en_US.utf8 |            |           | \n template0 | postgres | UTF8     | libc            | en_US.utf8 | en_US.utf8 |            |           | =c\/postgres          +\n           |          |          |                 |            |            |            |           | postgres=CTc\/postgres\n template1 | postgres | UTF8     | libc            | en_US.utf8 | en_US.utf8 |            |           | =c\/postgres          +\n           |          |          |                 |            |            |            |           | postgres=CTc\/postgres\n(4 rows)\n\npostgres=# \n\n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\">Now we are fine and the size of the WAL segments is as well as we wanted to have it:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: sql; highlight: [1]; title: ; notranslate\" title=\"\">\npostgres=# show wal_segment_size;\n wal_segment_size \n------------------\n 32MB\n(1 row)\n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\">Data checksum are enabled:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: sql; highlight: [1]; title: ; notranslate\" title=\"\">\npostgres=# \\! pg_controldata | grep checksum\nData page checksum version:           1\n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\">We could have changed the encoding, but as the default anyway is &#8220;UTF8&#8221;, there is no reason to touch this usually.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Another option you have, is to execute SQL commands or whole scripts (via <a href=\"https:\/\/kubernetes.io\/docs\/concepts\/configuration\/configmap\/\">ConfigMaps<\/a>). A simple example is this one:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; highlight: [1,23,25,27,29,33]; title: ; notranslate\" title=\"\">\nminicube@micro-minicube:~&amp;gt; cat pg.yaml \napiVersion: postgresql.cnpg.io\/v1\nkind: Cluster\nmetadata:\n  name: my-pg-cluster\nspec:\n  instances: 3\n\n  bootstrap:\n    initdb:\n      database: db1\n      owner: db1\n      dataChecksums: true\n      walSegmentSize: 32\n      localeCollate: &#039;en_US.utf8&#039;\n      localeCType: &#039;en_US.utf8&#039;\n      postInitSQL:\n      - create user db2\n      - create database db2 with owner = db2\n  storage:\n    size: 1Gi\n\nminicube@micro-minicube:~&amp;gt; kubectl delete -f pg.yaml \ncluster.postgresql.cnpg.io &quot;my-pg-cluster&quot; deleted\nminicube@micro-minicube:~&amp;gt; kubectl apply -f pg.yaml\ncluster.postgresql.cnpg.io\/my-pg-cluster created\nminicube@micro-minicube:~&amp;gt; kubectl exec my-pg-cluster-1 -i -t -- \/bin\/bash\nDefaulted container &quot;postgres&quot; out of: postgres, bootstrap-controller (init)\npostgres@my-pg-cluster-1:\/$ psql\npsql (16.2 (Debian 16.2-1.pgdg110+2))\nType &quot;help&quot; for help.\n\npostgres=# \\l\n                                                      List of databases\n   Name    |  Owner   | Encoding | Locale Provider |  Collate   |   Ctype    | ICU Locale | ICU Rules |   Access privileges   \n-----------+----------+----------+-----------------+------------+------------+------------+-----------+-----------------------\n db1       | db1      | UTF8     | libc            | en_US.utf8 | en_US.utf8 |            |           | \n db2       | db2      | UTF8     | libc            | en_US.utf8 | en_US.utf8 |            |           | \n postgres  | postgres | UTF8     | libc            | en_US.utf8 | en_US.utf8 |            |           | \n template0 | postgres | UTF8     | libc            | en_US.utf8 | en_US.utf8 |            |           | =c\/postgres          +\n           |          |          |                 |            |            |            |           | postgres=CTc\/postgres\n template1 | postgres | UTF8     | libc            | en_US.utf8 | en_US.utf8 |            |           | =c\/postgres          +\n           |          |          |                 |            |            |            |           | postgres=CTc\/postgres\n(5 rows)\n\npostgres=# \n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\">All this is <a href=\"https:\/\/cloudnative-pg.io\/documentation\/1.23\/bootstrap\/\">documented<\/a>, of course. In the next post we&#8217;ll look at how we can configure PostgreSQL, because bootstrapping is one task, but configuring PostgreSQL for your needs is another task you definitely should look at.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In the last post we&#8217;ve created a very simple three node PostgreSQL cluster using CloudNativePG and this was really easy to do. While this is great to get started quickly, you usually want to have more control on how PostgreSQL is initialized and configured. In this post we&#8217;ll look at bootstrapping the cluster and what&hellip;&nbsp;<\/p>\n","protected":false},"author":28,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"neve_meta_sidebar":"","neve_meta_container":"","neve_meta_enable_content_width":"","neve_meta_content_width":0,"neve_meta_title_alignment":"","neve_meta_author_avatar":"","neve_post_elements_order":"","neve_meta_disable_header":"","neve_meta_disable_footer":"","neve_meta_disable_title":"","neve_meta_reading_time":"","_themeisle_gutenberg_block_has_review":false,"footnotes":""},"categories":[955,4133,1320],"tags":[],"class_list":["post-33433","post","type-post","status-publish","format-standard","category-cloud","category-database","category-devops"],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v28.8 (Yoast SEO v28.8) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>CloudnativePG - Bootstrapping an empty cluster - dbi services Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/cloudnativepg-bootstrapping-an-empty-cluster\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"CloudnativePG - Bootstrapping an empty cluster\" \/>\n<meta property=\"og:description\" content=\"In the last post we&#8217;ve created a very simple three node PostgreSQL cluster using CloudNativePG and this was really easy to do. While this is great to get started quickly, you usually want to have more control on how PostgreSQL is initialized and configured. In this post we&#8217;ll look at bootstrapping the cluster and what&hellip;&nbsp;\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/cloudnativepg-bootstrapping-an-empty-cluster\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi services Blog\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/dbiservices\/\" \/>\n<meta property=\"article:published_time\" content=\"2024-06-08T12:28:01+00:00\" \/>\n<meta name=\"author\" content=\"Open source Team\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@dbiservices\" \/>\n<meta name=\"twitter:site\" content=\"@dbiservices\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Open source Team\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"2 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/cloudnativepg-bootstrapping-an-empty-cluster\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/cloudnativepg-bootstrapping-an-empty-cluster\\\/\"},\"author\":{\"name\":\"Open source Team\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/0b4548362cac3eeff8b3eaf329e3530a\"},\"headline\":\"CloudnativePG &#8211; Bootstrapping an empty cluster\",\"datePublished\":\"2024-06-08T12:28:01+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/cloudnativepg-bootstrapping-an-empty-cluster\\\/\"},\"wordCount\":368,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/#organization\"},\"articleSection\":[\"Cloud\",\"Database\",\"DevOps\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/cloudnativepg-bootstrapping-an-empty-cluster\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/cloudnativepg-bootstrapping-an-empty-cluster\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/cloudnativepg-bootstrapping-an-empty-cluster\\\/\",\"name\":\"CloudnativePG - Bootstrapping an empty cluster - dbi services Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\"},\"datePublished\":\"2024-06-08T12:28:01+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/cloudnativepg-bootstrapping-an-empty-cluster\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/cloudnativepg-bootstrapping-an-empty-cluster\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/cloudnativepg-bootstrapping-an-empty-cluster\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"CloudnativePG &#8211; Bootstrapping an empty cluster\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\",\"name\":\"dbi services Blog\",\"description\":\"#BeSharing\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/#organization\",\"name\":\"dbi services\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/dbi-services-logo.png\",\"contentUrl\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/dbi-services-logo.png\",\"width\":512,\"height\":512,\"caption\":\"dbi services\"},\"image\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/dbiservices\\\/\",\"https:\\\/\\\/x.com\\\/dbiservices\",\"https:\\\/\\\/www.linkedin.com\\\/company\\\/dbi-services\\\/\",\"https:\\\/\\\/www.youtube.com\\\/user\\\/dbiservices\"],\"description\":\"Swiss IT consulting and services company specialized in efficient data infrastructures and platforms: databases, application servers, cloud, DevOps, digitalization, analytics, data quality and monitoring. Headquartered in Del\u00e9mont with offices in Nyon, Basel, Bern and Zurich.\",\"email\":\"info@dbi-services.com\",\"telephone\":\"+41 32 422 96 00\",\"legalName\":\"dbi services SA\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/0b4548362cac3eeff8b3eaf329e3530a\",\"name\":\"Open source Team\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/2022\\\/05\\\/open-source-author.png\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/2022\\\/05\\\/open-source-author.png\",\"contentUrl\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/2022\\\/05\\\/open-source-author.png\",\"caption\":\"Open source Team\"},\"description\":\"Posts published under the Open source Team account are collective contributions by the dbi services open infrastructure consultants. The practice covers open-source databases and platforms, PostgreSQL first of all, along with MySQL, MariaDB, and Linux, from architecture, replication, and high availability to performance tuning and operations under service level agreements, and contributes actively to the PostgreSQL community.\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/author\\\/open-source-team\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"CloudnativePG - Bootstrapping an empty cluster - dbi services Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/cloudnativepg-bootstrapping-an-empty-cluster\/","og_locale":"en_US","og_type":"article","og_title":"CloudnativePG - Bootstrapping an empty cluster","og_description":"In the last post we&#8217;ve created a very simple three node PostgreSQL cluster using CloudNativePG and this was really easy to do. While this is great to get started quickly, you usually want to have more control on how PostgreSQL is initialized and configured. In this post we&#8217;ll look at bootstrapping the cluster and what&hellip;&nbsp;","og_url":"https:\/\/www.dbi-services.com\/blog\/cloudnativepg-bootstrapping-an-empty-cluster\/","og_site_name":"dbi services Blog","article_publisher":"https:\/\/www.facebook.com\/dbiservices\/","article_published_time":"2024-06-08T12:28:01+00:00","author":"Open source Team","twitter_card":"summary_large_image","twitter_creator":"@dbiservices","twitter_site":"@dbiservices","twitter_misc":{"Written by":"Open source Team","Est. reading time":"2 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/cloudnativepg-bootstrapping-an-empty-cluster\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/cloudnativepg-bootstrapping-an-empty-cluster\/"},"author":{"name":"Open source Team","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0b4548362cac3eeff8b3eaf329e3530a"},"headline":"CloudnativePG &#8211; Bootstrapping an empty cluster","datePublished":"2024-06-08T12:28:01+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/cloudnativepg-bootstrapping-an-empty-cluster\/"},"wordCount":368,"commentCount":0,"publisher":{"@id":"https:\/\/www.dbi-services.com\/#organization"},"articleSection":["Cloud","Database","DevOps"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/cloudnativepg-bootstrapping-an-empty-cluster\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/cloudnativepg-bootstrapping-an-empty-cluster\/","url":"https:\/\/www.dbi-services.com\/blog\/cloudnativepg-bootstrapping-an-empty-cluster\/","name":"CloudnativePG - Bootstrapping an empty cluster - dbi services Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2024-06-08T12:28:01+00:00","breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/cloudnativepg-bootstrapping-an-empty-cluster\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/cloudnativepg-bootstrapping-an-empty-cluster\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/cloudnativepg-bootstrapping-an-empty-cluster\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"CloudnativePG &#8211; Bootstrapping an empty cluster"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi services Blog","description":"#BeSharing","publisher":{"@id":"https:\/\/www.dbi-services.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.dbi-services.com\/#organization","name":"dbi services","url":"https:\/\/www.dbi-services.com\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2026\/09\/dbi-services-logo.png","contentUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2026\/09\/dbi-services-logo.png","width":512,"height":512,"caption":"dbi services"},"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/dbiservices\/","https:\/\/x.com\/dbiservices","https:\/\/www.linkedin.com\/company\/dbi-services\/","https:\/\/www.youtube.com\/user\/dbiservices"],"description":"Swiss IT consulting and services company specialized in efficient data infrastructures and platforms: databases, application servers, cloud, DevOps, digitalization, analytics, data quality and monitoring. Headquartered in Del\u00e9mont with offices in Nyon, Basel, Bern and Zurich.","email":"info@dbi-services.com","telephone":"+41 32 422 96 00","legalName":"dbi services SA"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0b4548362cac3eeff8b3eaf329e3530a","name":"Open source Team","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2022\/05\/open-source-author.png","url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2022\/05\/open-source-author.png","contentUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2022\/05\/open-source-author.png","caption":"Open source Team"},"description":"Posts published under the Open source Team account are collective contributions by the dbi services open infrastructure consultants. The practice covers open-source databases and platforms, PostgreSQL first of all, along with MySQL, MariaDB, and Linux, from architecture, replication, and high availability to performance tuning and operations under service level agreements, and contributes actively to the PostgreSQL community.","url":"https:\/\/www.dbi-services.com\/blog\/author\/open-source-team\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/33433","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/28"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=33433"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/33433\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=33433"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=33433"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=33433"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}