scaleway.RedisCluster

The type of Redis™ cluster you want to create (e.g. RED1-M).

Important: Updates to node_type will migrate the Redis™ cluster to the desired node_type. Keep in mind that you cannot downgrade a Redis™ cluster.

Redis™ cluster's version (e.g. 6.2.7).

Important: Updates to version will migrate the Redis™ cluster to the desired version. Keep in mind that you cannot downgrade a Redis™ cluster.

The number of nodes in the Redis™ cluster.

Important: You cannot set cluster_size to 2, you either have to choose Standalone mode (1 node) or cluster mode which is minimum 3 (1 main node + 2 secondary nodes)

Important: If you are using the cluster mode (>=3 nodes), you can set a bigger cluster_size than you initially did, it will migrate the Redis™ cluster but keep in mind that you cannot downgrade a Redis™ cluster, so setting a smaller cluster_size will destroy and recreate your cluster.

Important: If you are using the Standalone mode (1 node), setting a bigger cluster_size will destroy and recreate your cluster as you will be switching to the cluster mode.

(Optional) Public network details. Only one of private_network and public_network may be set.

The public_network block exports:

Whether TLS is enabled or not.

The changes on tls_enabled will force the resource creation.

The type of Redis™ cluster you want to create (e.g. RED1-M).

Important: Updates to node_type will migrate the Redis™ cluster to the desired node_type. Keep in mind that you cannot downgrade a Redis™ cluster.

Redis™ cluster's version (e.g. 6.2.7).

Important: Updates to version will migrate the Redis™ cluster to the desired version. Keep in mind that you cannot downgrade a Redis™ cluster.

The number of nodes in the Redis™ cluster.

Important: You cannot set cluster_size to 2, you either have to choose Standalone mode (1 node) or cluster mode which is minimum 3 (1 main node + 2 secondary nodes)

Important: If you are using the cluster mode (>=3 nodes), you can set a bigger cluster_size than you initially did, it will migrate the Redis™ cluster but keep in mind that you cannot downgrade a Redis™ cluster, so setting a smaller cluster_size will destroy and recreate your cluster.

Important: If you are using the Standalone mode (1 node), setting a bigger cluster_size will destroy and recreate your cluster as you will be switching to the cluster mode.

(Optional) Public network details. Only one of private_network and public_network may be set.

The public_network block exports:

Whether TLS is enabled or not.

The changes on tls_enabled will force the resource creation.

The type of Redis™ cluster you want to create (e.g. RED1-M).

Important: Updates to node_type will migrate the Redis™ cluster to the desired node_type. Keep in mind that you cannot downgrade a Redis™ cluster.

Redis™ cluster's version (e.g. 6.2.7).

Important: Updates to version will migrate the Redis™ cluster to the desired version. Keep in mind that you cannot downgrade a Redis™ cluster.

The number of nodes in the Redis™ cluster.

Important: You cannot set cluster_size to 2, you either have to choose Standalone mode (1 node) or cluster mode which is minimum 3 (1 main node + 2 secondary nodes)

Important: If you are using the cluster mode (>=3 nodes), you can set a bigger cluster_size than you initially did, it will migrate the Redis™ cluster but keep in mind that you cannot downgrade a Redis™ cluster, so setting a smaller cluster_size will destroy and recreate your cluster.

Important: If you are using the Standalone mode (1 node), setting a bigger cluster_size will destroy and recreate your cluster as you will be switching to the cluster mode.

(Optional) Public network details. Only one of private_network and public_network may be set.

The public_network block exports:

Whether TLS is enabled or not.

The changes on tls_enabled will force the resource creation.

The type of Redis™ cluster you want to create (e.g. RED1-M).

Important: Updates to node_type will migrate the Redis™ cluster to the desired node_type. Keep in mind that you cannot downgrade a Redis™ cluster.

Redis™ cluster's version (e.g. 6.2.7).

Important: Updates to version will migrate the Redis™ cluster to the desired version. Keep in mind that you cannot downgrade a Redis™ cluster.

The number of nodes in the Redis™ cluster.

Important: You cannot set cluster_size to 2, you either have to choose Standalone mode (1 node) or cluster mode which is minimum 3 (1 main node + 2 secondary nodes)

Important: If you are using the cluster mode (>=3 nodes), you can set a bigger cluster_size than you initially did, it will migrate the Redis™ cluster but keep in mind that you cannot downgrade a Redis™ cluster, so setting a smaller cluster_size will destroy and recreate your cluster.

Important: If you are using the Standalone mode (1 node), setting a bigger cluster_size will destroy and recreate your cluster as you will be switching to the cluster mode.

(Optional) Public network details. Only one of private_network and public_network may be set.

The public_network block exports:

Whether TLS is enabled or not.

The changes on tls_enabled will force the resource creation.

The type of Redis™ cluster you want to create (e.g. RED1-M).

Important: Updates to node_type will migrate the Redis™ cluster to the desired node_type. Keep in mind that you cannot downgrade a Redis™ cluster.

Redis™ cluster's version (e.g. 6.2.7).

Important: Updates to version will migrate the Redis™ cluster to the desired version. Keep in mind that you cannot downgrade a Redis™ cluster.

The number of nodes in the Redis™ cluster.

Important: You cannot set cluster_size to 2, you either have to choose Standalone mode (1 node) or cluster mode which is minimum 3 (1 main node + 2 secondary nodes)

Important: If you are using the cluster mode (>=3 nodes), you can set a bigger cluster_size than you initially did, it will migrate the Redis™ cluster but keep in mind that you cannot downgrade a Redis™ cluster, so setting a smaller cluster_size will destroy and recreate your cluster.

Important: If you are using the Standalone mode (1 node), setting a bigger cluster_size will destroy and recreate your cluster as you will be switching to the cluster mode.

(Optional) Public network details. Only one of private_network and public_network may be set.

The public_network block exports:

Whether TLS is enabled or not.

The changes on tls_enabled will force the resource creation.

The type of Redis™ cluster you want to create (e.g. RED1-M).

Important: Updates to node_type will migrate the Redis™ cluster to the desired node_type. Keep in mind that you cannot downgrade a Redis™ cluster.

Redis™ cluster's version (e.g. 6.2.7).

Important: Updates to version will migrate the Redis™ cluster to the desired version. Keep in mind that you cannot downgrade a Redis™ cluster.

The number of nodes in the Redis™ cluster.

Important: You cannot set cluster_size to 2, you either have to choose Standalone mode (1 node) or cluster mode which is minimum 3 (1 main node + 2 secondary nodes)

Important: If you are using the cluster mode (>=3 nodes), you can set a bigger cluster_size than you initially did, it will migrate the Redis™ cluster but keep in mind that you cannot downgrade a Redis™ cluster, so setting a smaller cluster_size will destroy and recreate your cluster.

Important: If you are using the Standalone mode (1 node), setting a bigger cluster_size will destroy and recreate your cluster as you will be switching to the cluster mode.

(Optional) Public network details. Only one of private_network and public_network may be set.

The public_network block exports:

Whether TLS is enabled or not.

The changes on tls_enabled will force the resource creation.

A text describing this rule. Default description: Allow IP

The acl conflict with private_network. Only one should be specified.

A text describing this rule. Default description: Allow IP

The acl conflict with private_network. Only one should be specified.

A text describing this rule. Default description: Allow IP

The acl conflict with private_network. Only one should be specified.

A text describing this rule. Default description: Allow IP

The acl conflict with private_network. Only one should be specified.

A text describing this rule. Default description: Allow IP

The acl conflict with private_network. Only one should be specified.

A text describing this rule. Default description: Allow IP

The acl conflict with private_network. Only one should be specified.

Endpoint IPv4 addresses in CIDR notation. You must provide at least one IP per node. Keep in mind that in cluster mode you cannot edit your Private Network after its creation so if you want to be able to scale your cluster horizontally (adding nodes) later, you should provide more IPs than nodes. If not set, the IP network address within the private subnet is determined by the IP Address Management (IPAM) service.

The private_network conflicts with acl. Only one should be specified.

Important: The way to use Private Networks differs whether you are using Redis™ in Standalone or cluster mode.

• Standalone mode (cluster_size = 1) : you can attach as many Private Networks as you want (each must be a separate block). If you detach your only Private Network, your cluster won't be reachable until you define a new Private or Public Network. You can modify your private_network and its specs, you can have both a Private and Public Network side by side.

• Cluster mode (cluster_size > 2) : you can define a single Private Network as you create your cluster, you won't be able to edit or detach it afterward, unless you create another cluster. This also means that, if you are using a static configuration (service_ips), you won't be able to scale your cluster horizontally (add more nodes) since it would require updating the Private Network to add IPs. Your service_ips must be listed as follows:

import * as pulumi from "@pulumi/pulumi";

import pulumi

using System.Collections.Generic;
using System.Linq;
using Pulumi;
return await Deployment.RunAsync(() =>
{
});

package main

import (
	"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)

func main() {
	pulumi.Run(func(ctx *pulumi.Context) error {
		return nil
	})
}

package generated_program;

import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;

public class App {
    public static void main(String[] args) {
        Pulumi.run(App::stack);
    }

    public static void stack(Context ctx) {
    }
}

{}

Endpoint IPv4 addresses in CIDR notation. You must provide at least one IP per node. Keep in mind that in cluster mode you cannot edit your Private Network after its creation so if you want to be able to scale your cluster horizontally (adding nodes) later, you should provide more IPs than nodes. If not set, the IP network address within the private subnet is determined by the IP Address Management (IPAM) service.

The private_network conflicts with acl. Only one should be specified.

Important: The way to use Private Networks differs whether you are using Redis™ in Standalone or cluster mode.

• Standalone mode (cluster_size = 1) : you can attach as many Private Networks as you want (each must be a separate block). If you detach your only Private Network, your cluster won't be reachable until you define a new Private or Public Network. You can modify your private_network and its specs, you can have both a Private and Public Network side by side.

• Cluster mode (cluster_size > 2) : you can define a single Private Network as you create your cluster, you won't be able to edit or detach it afterward, unless you create another cluster. This also means that, if you are using a static configuration (service_ips), you won't be able to scale your cluster horizontally (add more nodes) since it would require updating the Private Network to add IPs. Your service_ips must be listed as follows:

import * as pulumi from "@pulumi/pulumi";

import pulumi

using System.Collections.Generic;
using System.Linq;
using Pulumi;
return await Deployment.RunAsync(() =>
{
});

package main

import (
	"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)

func main() {
	pulumi.Run(func(ctx *pulumi.Context) error {
		return nil
	})
}

package generated_program;

import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;

public class App {
    public static void main(String[] args) {
        Pulumi.run(App::stack);
    }

    public static void stack(Context ctx) {
    }
}

{}

Endpoint IPv4 addresses in CIDR notation. You must provide at least one IP per node. Keep in mind that in cluster mode you cannot edit your Private Network after its creation so if you want to be able to scale your cluster horizontally (adding nodes) later, you should provide more IPs than nodes. If not set, the IP network address within the private subnet is determined by the IP Address Management (IPAM) service.

The private_network conflicts with acl. Only one should be specified.

Important: The way to use Private Networks differs whether you are using Redis™ in Standalone or cluster mode.

• Standalone mode (cluster_size = 1) : you can attach as many Private Networks as you want (each must be a separate block). If you detach your only Private Network, your cluster won't be reachable until you define a new Private or Public Network. You can modify your private_network and its specs, you can have both a Private and Public Network side by side.

• Cluster mode (cluster_size > 2) : you can define a single Private Network as you create your cluster, you won't be able to edit or detach it afterward, unless you create another cluster. This also means that, if you are using a static configuration (service_ips), you won't be able to scale your cluster horizontally (add more nodes) since it would require updating the Private Network to add IPs. Your service_ips must be listed as follows:

import * as pulumi from "@pulumi/pulumi";

import pulumi

using System.Collections.Generic;
using System.Linq;
using Pulumi;
return await Deployment.RunAsync(() =>
{
});

package main

import (
	"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)

func main() {
	pulumi.Run(func(ctx *pulumi.Context) error {
		return nil
	})
}

package generated_program;

import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;

public class App {
    public static void main(String[] args) {
        Pulumi.run(App::stack);
    }

    public static void stack(Context ctx) {
    }
}

{}

Endpoint IPv4 addresses in CIDR notation. You must provide at least one IP per node. Keep in mind that in cluster mode you cannot edit your Private Network after its creation so if you want to be able to scale your cluster horizontally (adding nodes) later, you should provide more IPs than nodes. If not set, the IP network address within the private subnet is determined by the IP Address Management (IPAM) service.

The private_network conflicts with acl. Only one should be specified.

Important: The way to use Private Networks differs whether you are using Redis™ in Standalone or cluster mode.

• Standalone mode (cluster_size = 1) : you can attach as many Private Networks as you want (each must be a separate block). If you detach your only Private Network, your cluster won't be reachable until you define a new Private or Public Network. You can modify your private_network and its specs, you can have both a Private and Public Network side by side.

• Cluster mode (cluster_size > 2) : you can define a single Private Network as you create your cluster, you won't be able to edit or detach it afterward, unless you create another cluster. This also means that, if you are using a static configuration (service_ips), you won't be able to scale your cluster horizontally (add more nodes) since it would require updating the Private Network to add IPs. Your service_ips must be listed as follows:

import * as pulumi from "@pulumi/pulumi";

import pulumi

using System.Collections.Generic;
using System.Linq;
using Pulumi;
return await Deployment.RunAsync(() =>
{
});

package main

import (
	"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)

func main() {
	pulumi.Run(func(ctx *pulumi.Context) error {
		return nil
	})
}

package generated_program;

import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;

public class App {
    public static void main(String[] args) {
        Pulumi.run(App::stack);
    }

    public static void stack(Context ctx) {
    }
}

{}

Endpoint IPv4 addresses in CIDR notation. You must provide at least one IP per node. Keep in mind that in cluster mode you cannot edit your Private Network after its creation so if you want to be able to scale your cluster horizontally (adding nodes) later, you should provide more IPs than nodes. If not set, the IP network address within the private subnet is determined by the IP Address Management (IPAM) service.

The private_network conflicts with acl. Only one should be specified.

Important: The way to use Private Networks differs whether you are using Redis™ in Standalone or cluster mode.

• Standalone mode (cluster_size = 1) : you can attach as many Private Networks as you want (each must be a separate block). If you detach your only Private Network, your cluster won't be reachable until you define a new Private or Public Network. You can modify your private_network and its specs, you can have both a Private and Public Network side by side.

• Cluster mode (cluster_size > 2) : you can define a single Private Network as you create your cluster, you won't be able to edit or detach it afterward, unless you create another cluster. This also means that, if you are using a static configuration (service_ips), you won't be able to scale your cluster horizontally (add more nodes) since it would require updating the Private Network to add IPs. Your service_ips must be listed as follows:

import * as pulumi from "@pulumi/pulumi";

import pulumi

using System.Collections.Generic;
using System.Linq;
using Pulumi;
return await Deployment.RunAsync(() =>
{
});

package main

import (
	"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)

func main() {
	pulumi.Run(func(ctx *pulumi.Context) error {
		return nil
	})
}

package generated_program;

import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;

public class App {
    public static void main(String[] args) {
        Pulumi.run(App::stack);
    }

    public static void stack(Context ctx) {
    }
}

{}

Endpoint IPv4 addresses in CIDR notation. You must provide at least one IP per node. Keep in mind that in cluster mode you cannot edit your Private Network after its creation so if you want to be able to scale your cluster horizontally (adding nodes) later, you should provide more IPs than nodes. If not set, the IP network address within the private subnet is determined by the IP Address Management (IPAM) service.

The private_network conflicts with acl. Only one should be specified.

Important: The way to use Private Networks differs whether you are using Redis™ in Standalone or cluster mode.

• Standalone mode (cluster_size = 1) : you can attach as many Private Networks as you want (each must be a separate block). If you detach your only Private Network, your cluster won't be reachable until you define a new Private or Public Network. You can modify your private_network and its specs, you can have both a Private and Public Network side by side.

• Cluster mode (cluster_size > 2) : you can define a single Private Network as you create your cluster, you won't be able to edit or detach it afterward, unless you create another cluster. This also means that, if you are using a static configuration (service_ips), you won't be able to scale your cluster horizontally (add more nodes) since it would require updating the Private Network to add IPs. Your service_ips must be listed as follows:

import * as pulumi from "@pulumi/pulumi";

import pulumi

using System.Collections.Generic;
using System.Linq;
using Pulumi;
return await Deployment.RunAsync(() =>
{
});

package main

import (
	"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)

func main() {
	pulumi.Run(func(ctx *pulumi.Context) error {
		return nil
	})
}

package generated_program;

import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;

public class App {
    public static void main(String[] args) {
        Pulumi.run(App::stack);
    }

    public static void stack(Context ctx) {
    }
}

{}