USDadding worker nodesApplyThe Arc Deployment extension has been replaced by the Arc extension and has been uninstalled.Azure Arc ResourcesAvailableBackupBackups{0} backupsBusinessCriticalCancelClick the new support request button to file a support request in the Azure Portal.Click the troubleshoot button to open the Azure Arc {0} troubleshooting notebook.ComputeCompute + Storagethere are sufficient resources availableBefore doing so, you need to ensurein your Kubernetes cluster to honor this configuration.without downtime and byConditionConfigurationConfiguration (per node)Configure retention policyConfigure Retention PolicyConfirm the new passwordConnect to ServerConnectConnect to Existing ControllerCould not connect to controller {0}. {1}Connect to SQL managed instance - Azure Arc ({0})Could not connect to SQL managed instance - Azure Arc Instance {0}. {1}Connect to PostgreSQL Hyperscale - Azure Arc ({0})Could not connect to PostgreSQL Hyperscale - Azure Arc Instance {0}. {1}A connection to the server is required to show and set database engine settings, which will require the PostgreSQL Extension to be installed.Connection ModeConnection string for {0}{0} is the name of the type of connection string (e.g. Java)Connection StringsPod containers are ready.Cluster ContextAzure Arc Data Controller Dashboard - {0}Kube Config File PathNameThe name to display in the tree view, this is not applied to the controller itself.Controller PasswordController URLThe Controller URL is necessary if there are multiple clusters with the same namespace - this should generally not be necessary.https://<IP or hostname>:<port>Controller UsernameCoordinatorCoordinator Node CPU limitCoordinator Node CPU requestCoordinator endpointCoordinator Node Memory limit (in GB)Coordinator Node Memory request (in GB)Coordinator NodeYou can configure the number of CPU cores and storage size that will apply to the coordinator node. Adjust the number of CPU cores and memory settings for your server group. To reset the requests and/or limits, pass in empty value.Coordinator Node Parameters These server parameters of the Coordinator node can be set to custom (non-default) values. Search to find parameters.{0} copied to clipboardCopy {0} Connection String to clipboard{0} is the name of the type of connection string (e.g. Java)Copy {0} to clipboard{0} is the name of the type of value being copied (e.g. Coordinator endpoint)CPU limitCPU requestCould not find Azure resource for {0}Could not find controller registration.New InstanceData controllerAzure Arc Data Controller{0} dataDatabaseDatabase {0} createdFailed to create database {0}. {1}Destination DetailsEnter the required settings for target database name and SQL managed instance. By default, the source managed instance is selected.Database nameDatabasesarc-dcDeleteDeleting instance '{0}'...DescriptionDetailsDiagnose and solve problemsDirectDiscardDropCurrently dropping another extension, try again once that is completed.Earliest point in timeEmergencyEndpointEnter a non empty password or press escape to exit.Enter a new passwordError connecting to controller. {0}Error encountered while verifying password. {0}Failed to install extension {0}.Extension '{0}' has been installed.Extension namePostgreSQL provides the ability to extend the functionality of your database by using extensions.Value should be either of the following: ({0}).Some extensions must be loaded into PostgreSQL at startup time before they can be used. To edit, type in comma separated list of valid extensions: ({0}).ExtensionsExtensions '{0}' addedPostgreSQL provides the ability to extend the functionality of your database by using extensions. Extensions allow for bundling multiple related SQL objects together in a single package that can be loaded or removed from your database with a single command. After being loaded in the database, extensions can function like built-in features.Extensions '{0}' droppedSome extensions must be loaded into PostgreSQL at startup time before they can be used. These preloaded extensions can be viewed and edited below.Learn more about PostgreSQL extensions.Table of preloaded extensions.Table of preloaded extensions are loading.Preloaded extensions can now be viewed.External EndpointFailedFeedbackAn unexpected error occurred retrieving the config for '{0}'. {1}An unexpected error occurred retrieving the databases for '{0}'. {1}An unexpected error occurred retrieving the endpoints for '{0}'. {1}An unexpected error occurred retrieving the engine settings for '{0}'. {1}An unexpected error occurred retrieving the registrations for '{0}'. {1}Fully qualified domainGeneralPurposeGrafana DashboardDashboard for viewing metricsIndirectInstalling extension '{0}'...InstanceInstance '{0}' deletedFailed to delete instance {0}. {1}Warning! Deleting an instance is permanent and cannot be undone. To delete the instance '{0}' type the name '{0}' below to proceed.Failed to update instance {0}. {1}Instance '{0}' updatedInvalid config pathThe value '{0}' does not match the instance name. Try again or press escape to exitIssues DetectedKibana DashboardDashboard for viewing logsLast transitionLatest point in timeLearn more about database engine settings for Azure Arc-enabled PostgreSQL HyperscaleLearn more about Azure PostgreSQL Hyperscale client interfacesLearn More.Load extensionsLoading...Loading cluster contexts completedError loading cluster contexts. {0}{0} logError logging into controller - wrong username or passwordMemory limit (in GB)Memory request (in GB)Managed instance adminDatabases with available backups are displayed below. Restore databases to this instance or any other instance within the same custom location.You can scale your Azure SQL managed instance - Azure Arc byA connection is required to list the databases on this instance.SQL managed instance - Azure Arc Dashboard - {0}MSSQLSQL managed instance - Azure ArcThe {0} extension is required to view engine settings. Do you wish to install it now?MonitorNameNamespaceNetworkingNew DatabaseNew support requestNoNo extensions listed in configuration.No External Endpoint has been configured so this information isn't available.No instances availableNo worker server parameters found...There aren’t any known issues affecting this PostgreSQL Hyperscale instance.No worker pods in this configuration.nodeNode configurationnodesNot ConfiguredNot Ready{0} vCore{0} vCores• {0} ({1} issues)OffOfflineOkOnOnlineError opening dashboard. {0}Open in Azure PortalOverviewFailed to discard user input. {0}Parameter NamePasswordFailed to acquire password. {0}Password reset successfullyFailed to reset password. {0}Provide Password to ControllerPendingA connection is required to show and set database engine settings.PostgreSQL Hyperscale - Azure ArcPoint in time restoreSpecify how long you want to keep your point-in-time backups. Customize this for backup availability.Pod conditions tablePod is initialized.The pods listed below are experiencing issues that may affect performance or availability.Pod is ready.Pod is schedulable.Pods Presentpods readySelect a pod in the dropdown below for detailed health information.Select a pod in the dropdown below for detailed health informationPostgreSQL Hyperscale server group byAdmin usernameAzure Database for PostgreSQL - Azure ArcYou can scale your Azure Arc-enabledPostgreSQL Hyperscale - Azure Arc Dashboard - {0}microsoft.azuredatastudio-postgresqlPGSQLPostgreSQL versionPreloaded ExtensionsProject DetailsSelect the subscription to manage deployed resources. Use resource groups like folders to organize and manage all your resources.PropertiesRAMValue is expected to be in the range {0} - {1}ReadyRecoveringRecovery PendingRefreshRefresh failed. {0}Refresh node to enter credentialsRegionRemember Password132Reset all to defaultReset failed. {0}Reset PasswordReset to defaultResource GroupResource healthResource health can tell you if your resource is running as expected.RestoreRestore DatabaseRestore a database to an Azure Arc enabled SQL Managed Instance.Restore point (UTC), in a time format: 'YYYY-MM-DDTHH:MM:SSZRestore Point DetailsProvide time in correct format and within range: {0} to {1}Enter a restore point in the specified time format within given range of earliest and latest restore time.Point in time restore time window update failed. {0}RestoringPoint-In-Time Recovery retention (days)RunningSavescaling compute vCores and memory.Search to filter items...SecuritySelect from available client connection strings below.Server EndpointServer group nodesServer group typeService endpointsService endpoints tableSettingsSource databaseSource DetailsSelect a backup source and provide details. Additional settings will be defaulted where possible based on the selected database.StateStatusstorage per nodeSubscriptionSubscription IDSupport + troubleshootingNote that the resource configuration must have been uploaded to Azure first in order to open a support request.SuspectThe passwords do not match. Confirm the password or press escape to exit.TroubleshootTypeUnknownUnload extensionsEditing extensions failed. {0}Updated {0}Updating instance '{0}'...User cancelled the dialogUsernamevCoresValueWorkerWorker Nodes CPU limitWorker Nodes CPU requestWorker Nodes Memory limit (in GB)Worker Nodes Memory request (in GB)Worker node countIt is possible to scale in and out your server group by reducing or increasing the number of worker nodes. The value must be 0 or greater than 1.Worker Node ParametersWorker NodesYou can configure the number of CPU cores and storage size that will apply to all worker nodes. Adjust the number of CPU cores and memory settings for your server group. To reset the requests and/or limits, pass in empty value.Expand your server group and scale your database by adding worker nodes. These server parameters of the Worker nodes can be set to custom (non-default) values. Search to find parameters.Value of 1 is not supported.YesSelectThe cluster context information specified by config file: {0} and cluster context: {1} is no longer valid. Error is:
{2}
Do you want to update this information?Cluster Context with name: {0} not found in the Kube config fileBrowseAttempt to get isPassword for unknown variable:{0}Attempt to get variable value for unknown variable:{0}No 'contexts' found in the config file: {0}Controller Info could not be found with name: {0}No Azure Arc controllers are currently connected. Please run the command: 'Connect to Existing Azure Arc Controller' and then try againNo current cluster context was found in the kube config fileNo context is marked as 'current-context' in the config file: {0}No name field was found in a cluster context in the config file: {0}Password could not be retrieved for controller: {0} and user did not provide a password. Please retry later.I accept {0} and {1}.Azure Arc-enabled PostgreSQL Hyperscale terms and conditionsAzure Arc enabled Managed Instance provides SQL Server access and feature compatibility that can be deployed on the infrastructure of your choice. {0}Learn moreLearn more about Azure Arc enabled Managed InstanceAzure SQL managed instance - Azure Arc terms and conditionsAzure accountAzure locationAzure resource groupAzure informationAzure subscriptionAzure ArcConfirm passwordTarget Azure Arc ControllerCores LimitCores RequestI accept {0} and {1}.Auto-upload LogsEnable the automatic upload of logs. Direct mode only.Auto-upload MetricsEnable the automatic upload of metrics. Direct mode only.Config profileLoading config profilesLoading config profiles completeChoose the config profileWhat is your target existing Kubernetes cluster environment?Connectivity modeAzure ConfigurationController ConfigurationReview your configurationCustom LocationThe name of the custom location. Direct mode only.For indirect mode, provide a namespace, name and storage class for your Azure Arc data controller. This name will be used to identify your Arc instance for remote management and monitoring. For direct mode you do not need to provide a namespace, but please provide the custom location name.Data controller detailsInfrastructureCluster contextLocationConfirm passwordPasswordEnter the password that will be used to log in to the metrics and logs dashboards.Metrics and Logs Dashboard CredentialsUsernameEnter the username that will be used for the metrics and logs dashboards.Data controller nameName must consist of lower case alphanumeric characters, '-' or '.', start/end with an alphanumeric character and be 253 characters or less in length.Data controller namespaceIndirect mode only.Namespace must consist of lower case alphanumeric characters or '-', start/end with an alphanumeric character, and be 63 characters or fewer in length.Create Azure Arc data controllerSelect the subscription to manage deployed resources and costs. Use resource groups like folders to organize and manage all your resources.Azure detailsRead moreSelect from existing Kubernetes clustersby MicrosoftAzure Arc data controllerTerms of usePrivacy policy|AzureCluster contextControllerData controller infrastructureData controller nameData controller namespaceEstimated cost per monthFreeKube config file pathKubernetesLocationConfig profileResource groupSubscriptionTermsBy clicking 'Script to notebook', I (a) agree to the legal terms and privacy statement(s) associated with the Marketplace offering(s) listed above; (b) authorize Microsoft to bill my current payment method for the fees associated with the offering(s), with the same billing frequency as my Azure subscription; and (c) agree that Microsoft may share my contact, usage and transactional information with the provider(s) of the offering(s) for support, billing and other transactional activities. Microsoft does not provide rights for third-party offerings. For additional details see {0}.Azure Marketplace TermsUsernameSupport for Azure ArcAzure ArcMemory LimitMemory RequestManagePasswordThe maximum number of CPU cores for the Postgres instance that can be used on the coordinator node. Fractional cores are supported.CPU limitThe minimum number of CPU cores that must be available on the coordinator node to schedule the service. Fractional cores are supported.CPU requestThe memory limit of the Postgres instance on the coordinator node in GB.Memory limit (GB)The memory request of the Postgres instance on the coordinator node in GB.Memory request (GB)Engine VersionA comma-separated list of the Postgres extensions that should be loaded on startup. Please refer to the postgres documentation for supported values.ExtensionsServer group nameServer group name must consist of lower case alphanumeric characters or '-', start with a letter, end with an alphanumeric character, and be 11 characters or fewer in length.PortThe size of the storage volume to be used for backups in GB.Volume Size GB (Backups)The size of the storage volume to be used for data in GB.Volume Size GB (Data)The size of the storage volume to be used for logs in GB.Volume Size GB (Logs)The maximum number of CPU cores for the Postgres instance that can be used per node. Fractional cores are supported.CPU limit (cores per node)The minimum number of CPU cores that must be available per node to schedule the service. Fractional cores are supported.CPU request (cores per node)The number of worker nodes to provision in a sharded cluster, or zero (the default) for single-node Postgres.Number of workersThe memory limit of the Postgres instance per node in GB.Memory limit (GB per node)The memory request of the Postgres instance per node in GB.Memory request (GB per node)Coordinator Node Compute ConfigurationWorker Nodes Compute ConfigurationGeneral settingsStorage settingsThe storage class to be used for backup persistent volumesThe storage class to be used for data persistent volumesThe storage class to be used for logs persistent volumesProvide Azure enabled PostgreSQL Hyperscale server group parametersDeploy an Azure Arc-enabled PostgreSQL Hyperscale server groupSQL Connection informationThe cores limit of the managed instance as an integer.The request for cores of the managed instance as an integer.Cost SummaryAdditional charge per usage. See {0} for more detail.Administrator accountAzure Hybrid Benefit discount (in USD)BasicsBusiness CriticalCost per vCore (in USD)Custom locationEstimated cost per monthGeneral PurposeInstance nameManaged Instance admin loginpricing detailsResource groupService TierSelect from the latest vCore service tiers available for SQL Managed Instance - Azure Arc including General Purpose and Business Critical.Learn moreSQL Connection InformationSQL Instance SettingsSQL managed instance - Azure ArcSQL Managed Instance - Azure Arc Cost SummarySubscriptionCPU vCores LimitCheck the box to indicate this instance will be used for development or testing purposes only. This instance will not be billed.For development use onlyHigh availabilityEnable additional replicas for high availabilty. The compute and storage configuration selected below will be applied to all replicas.Instance nameSQL Instance Backup Retention PolicySQL Instance settingsInstance name must consist of lower case alphanumeric characters or '-', start with a letter, end with an alphanumeric character, and be 13 characters or fewer in length.sa username is disabled, please choose another usernameApply the Azure Hybrid Benefit if you already own a SQL Server LicenseI already have a SQL Server LicenseThe limit of the capacity of the managed instance as an integer.The request for the capacity of the managed instance as an integer amount of memory in GBs.1 replicaPoint in time restoreConfigure retention for point-in-time backups. {0}Specify how long you want to keep your point-in-time backups.Point in time retention (days)[PREVIEW] Business Critical (Unlimited vCores and RAM, advanced high availability)Select from the latest vCore service tiers available for SQL Managed Instance - Azure Arc including General Purpose and Business Critical.General Purpose (Up to 24 vCores and 128 Gi of RAM, standard high availability)Service TierThe storage class to be used for backup persistent volumes. If no value is specified, the default storage class will be used.The storage class to be used for data (.mdf). If no value is specified, the default storage class will be used.The storage class to be used for database logs (.ldf). If no value is specified, the default storage class will be used.The storage class to be used for all data and logs persistent volumes for all data controller pods that require them.The storage class to be used for logs (/var/log). If no value is specified, the default storage class will be used.by Microsoft3 replicas2 replicasUsernameThe size of the storage volume to be used for backups in gibibytes.Volume Size in Gi (Backups)The size of the storage volume to be used for data in gibibytes.Volume Size in Gi (Data)The size of the storage volume to be used for database logs in gibibytes.Volume Size in Gi (Database logs)The size of the storage volume to be used for logs in gibibytes.Volume Size in Gi (Logs)Provide Azure SQL managed instance parametersDeploy Azure SQL managed instance - Azure ArcStorage Class (Backups)Storage Class (Data)Storage Class (Database logs)Storage ClassStorage Class (Logs)Azure Arc ControllersNo Azure Arc controllers registered. [Learn More](https://azure.microsoft.com/services/azure-arc/)
[Connect Controller](command:arc.connectToController)Loading controllers...Connect to Existing Azure Arc ControllerCreate New Azure Arc ControllerEdit ConnectionEstimate Cost of SQL Managed Instance - Azure ArcRefreshRemove ControllerCores limit must be greater than or equal to requested coresDeployScript to notebookMemory limit must be greater than or equal to requested memoryMicrosoft Privacy StatementRequested cores must be less than or equal to cores limitRequested memory must be less than or equal to memory limitDeploy PostgreSQL Hyperscale server groups into an Azure Arc environmentPostgreSQL Hyperscale server groups - Azure ArcManaged SQL Instance service for app developers in a customer-managed environmentAzure SQL managed instance - Azure ArcCreates an Azure Arc data controllerAzure Arc data controllerValue must be an integerValue of 1 is not supported.