Update README.md

Author: ospillinger

README.md

@@ -8,7 +8,7 @@
 
 <br>
 
-Cortex deploys your machine learning models to your cloud infrastructure. You define your deployment with simple declarative configuration, Cortex containerizes your models, deploys them as scalable JSON APIs, and manages their lifecycle in production.
+Cortex deploys your machine learning models to your cloud infrastructure. You define your deployment with simple declarative configuration, Cortex containerizes your models, deploys them as autoscaling JSON APIs, and manages their lifecycle in production.
 
 Cortex is actively maintained by Cortex Labs. We're a venture-backed team of infrastructure engineers and [we're hiring](https://angel.co/cortex-labs-inc/jobs).
 
@@ -66,12 +66,12 @@ $ curl -d '{"a": 1, "b": 2, "c": 3}' https://amazonaws.com/my-api
 
 - **Machine learning deployments as code:** Cortex deployments are defined using declarative configuration.
 
+- **Autoscaling:** Cortex can automatically scale APIs to handle production workloads.
+
 - **Multi framework support:** Cortex supports TensorFlow, Keras, PyTorch, Scikit-learn, XGBoost, and more.
 
 - **CPU / GPU support:** Cortex can run inference on CPU or GPU infrastructure.
 
-- **Scalability:** Cortex can scale APIs to handle production workloads.
-
 - **Rolling updates:** Cortex updates deployed APIs without any downtime.
 
 - **Cloud native:** Cortex can be deployed on any AWS account in minutes.

manager/info.sh

@@ -26,8 +26,7 @@ function get_apis_endpoint() {
   kubectl -n=$CORTEX_NAMESPACE get service nginx-controller-apis -o json | tr -d '[:space:]' | sed 's/.*{\"hostname\":\"\(.*\)\".*/\1/'
 }
 
-echo
-eksctl utils write-kubeconfig --name=$CORTEX_CLUSTER
+eksctl utils write-kubeconfig --name=$CORTEX_CLUSTER  | grep -v "saved kubeconfig as" || true
 
 operator_endpoint=$(get_operator_endpoint)
 apis_endpoint=$(get_apis_endpoint)

manager/install_cortex.sh

@@ -24,26 +24,26 @@ function setup_bucket() {
 
   if ! aws s3api head-bucket --bucket $CORTEX_BUCKET --output json 2>/dev/null; then
     if aws s3 ls "s3://$CORTEX_BUCKET" --output json 2>&1 | grep -q 'NoSuchBucket'; then
-      echo -e "\n✓ Creating an S3 bucket: $CORTEX_BUCKET"
+      echo "✓ Creating an S3 bucket: $CORTEX_BUCKET"
       aws s3api create-bucket --bucket $CORTEX_BUCKET \
                               --region $CORTEX_REGION \
                               --create-bucket-configuration LocationConstraint=$CORTEX_REGION \
                               >/dev/null
     else
-      echo -e "\nA bucket named \"${CORTEX_BUCKET}\" already exists, but you do not have access to it"
+      echo "A bucket named \"${CORTEX_BUCKET}\" already exists, but you do not have access to it"
       exit 1
     fi
   else
-    echo -e "\n✓ Using an existing S3 bucket: $CORTEX_BUCKET"
+    echo "✓ Using an existing S3 bucket: $CORTEX_BUCKET"
   fi
 }
 
 function setup_cloudwatch_logs() {
   if ! aws logs list-tags-log-group --log-group-name $CORTEX_LOG_GROUP --region $CORTEX_REGION --output json 2>&1 | grep -q "\"tags\":"; then
-    echo -e "\n✓ Creating a CloudWatch log group: $CORTEX_LOG_GROUP"
+    echo "✓ Creating a CloudWatch log group: $CORTEX_LOG_GROUP"
     aws logs create-log-group --log-group-name $CORTEX_LOG_GROUP --region $CORTEX_REGION
   else
-    echo -e "\n✓ Using an existing CloudWatch log group: $CORTEX_LOG_GROUP"
+    echo "✓ Using an existing CloudWatch log group: $CORTEX_LOG_GROUP"
   fi
 }
 
@@ -143,15 +143,14 @@ function validate_cortex() {
     break
   done
 
-  echo -e "\n\n✓ Cortex is ready!"
+  echo -e "\n✓ Cortex is ready!"
 
   if command -v cortex >/dev/null; then
     echo -e "\nPlease run \`cortex configure\` to make sure your CLI is configured correctly"
   fi
 }
 
-echo
-eksctl utils write-kubeconfig --name=$CORTEX_CLUSTER
+eksctl utils write-kubeconfig --name=$CORTEX_CLUSTER | grep -v "saved kubeconfig as" || true
 
 echo -e "\nInstalling Cortex ..."
 

manager/uninstall_cortex.sh

@@ -16,8 +16,7 @@
 
 set -e
 
-echo
-eksctl utils write-kubeconfig --name=$CORTEX_CLUSTER
+eksctl utils write-kubeconfig --name=$CORTEX_CLUSTER | grep -v "saved kubeconfig as" || true
 
 echo -e "\nUninstalling Cortex ..."
 

manager/uninstall_operator.sh

@@ -18,8 +18,7 @@ set -e
 
 # Note: if namespace is changed, the old namespace will not be deleted
 
-echo
-eksctl utils write-kubeconfig --name=$CORTEX_CLUSTER
+eksctl utils write-kubeconfig --name=$CORTEX_CLUSTER | grep -v "saved kubeconfig as" || true
 
 echo -e "\nUninstalling the Cortex operator ..."