Roman's musings on IT, code, life
Recently I wanted to find a simple way to track and add upvotes for ideas such as feature requests. I ended up finding a pretty good spreadsheet template from Convas.io and making a few modifications.
You can copy and use my Google Sheet Voting Template here.
A Summary of the Official Building a Bolt JS App
Add a Shortcut in a Bolt JS Slack App
Recently I’ve been working a lot with kubernetes at my job. I’ve written up a bunch of internal documentation based on my work, and because it’s not company-specific I decided I’m going to share it here for anyone trying to find answers on the internet.
Table of Contents:
Check out kubernetes docs here: https://kubernetes.io/docs/home
Confirm the nodegroup you’re checking actually exists (e.g. you’re looking for pods running under engtools-infra/my-app) by listing all the nodegroups in a certain namespace:
k get nodegroup -n engtools-infra
Get the nodes under that nodegroup:
k get nodes -o wide | grep my-app
View pods under a node with the following command (replace NODE_NAME_GOES_HERE with the node’s name, e.g. ip-10-10-12-123.ec2.internal).
k get pod --field-selector=spec.nodeName=NODE_NAME_GOES_HERE -owide --all-namespaces | grep -v -E "( kube-proxy-| kube2iam-| local-volume-provisioner-| node-monitoring-| localusers-)"
Make sure you’re in the right cluster, get the deployment name, then use the rollout command.
k config current-context k get deployment -n [NAMESPACE] k rollout restart deployment [DEPLOYMENT_NAME] -n [NAMESPACE]
If you’re seeing errors about insufficient resources, or node(s) had taint … that the pod didn’t tolerate warnings, you probably need to define instanceType and resources attributes in your service k8s objects / charts. For example, something like the following:
instanceType: c5.2xlarge
resources:
requests:
cpu: "3"
memory: "4G"
limits:
cpu: "4"
memory: "6G"
A log you might see when deploying with Bazel is Deployment is not ready: <service>. 0 out of 2 expected pods are ready. This usually means k8s pods are in a CLB or some other non-ready status.
Use kubectl commands to check on the pods’ status and logs. Usual status check command:
kubectl -n NAMESPACE get pods
If you see CrashLoopBackOff status on one of your pods, that means it’s crashing (I know, thanks captain obvious).
Check the pod logs: k logs CRASHING_POD -n NAMESPACE.
Find the deployment.yaml file describing the launch instructions for this pod. Find the command attribute in that file, comment out the value underneath it, and add the following:
- tail
- "-f"
- /dev/null
Then re-deploy the pod. This will allow you to SSH into the pod, run the failing command manually, and generally get more info about the problem.
You might also need to comment out the liveness/readiness container specs in deployment.yaml, as those will often cause the pod to crash as well if there’s an issue with the primary container.
More info about troubleshooting crashloopbackoff pods can be found in this releasehub.com article.
Normal NotTriggerScaleUp 19m cluster-autoscaler pod didn’t trigger scale-up: 3 node(s) had taint {node: database-rev-eng-8c38-pool1}, that the pod didn’t tolerate…
Potentially a node group or a scaling group issue. For example, you might have a single AutoScalingGroup (asg) under your nodegroup-controller which has reached its max size. In this case, adding autoscaling: true option to your charts may be required in order to have more ASGs created.
If adding nodegroup options, you may need to delete the existing nodegroups (krm ng NODEGROUP_NAME -n NAMESPACE) for the option to take effect. After creating the new nodegroup, the cluster autoscaler may need to pass by, which can take a few minutes. So if you’re still seeing the scale-up messages and your pod in a Pending status after such a change you may need to give it a little time.
kubectl –context cluster3.us1.test.com get pods -n mynamespace
kube-ps1 will show you what cluster and namespace you’ve set in your prompt, which helps avoid this issue:
After installing it with homebrew, add this to your .rc file and restart your terminal to enable it:
source /usr/local/opt/kube-ps1/share/kube-ps1.sh PROMPT='$(kube_ps1)'$PROMPT
It works great in conjunction with using kubectx and kubens to change your context/cluster/namespace.
It’s very easy to change contexts in a different terminal and have a stale prompt showing the old context. Press enter to refresh the prompt.
If you use powerlevel10k, it can dynamically update your prompt with the current context when you’re typing a kubectl command – https://github.com/romkatv/powerlevel10k#show-on-command.
Troubleshooting
Recently my ‘clear formatting’ shortcut for most google apps (Command (or Cmd) ? + \) stopped working on my Macbook.
This was very frustrating as I use it all the time.
Apparently the 1password took over this shortcut since it uses cmd+\ to fill logins, silently. I was able to change the shortcut in 1password preferences, at which point clear formatting started working again.
In the future, if you have a similar issue, there’s also an app called ShortcutDetective that can help you find out if a keyboard shortcut is being used for an app on your Mac.
Confirm the nodegroup you’re checking actually exists (e.g. you’re looking for pods running under product-team/fubar) by listing all the nodegroups in a certain namespace:
get nodegroup -n product-teamGet the nodes under that nodegroup:
get nodes -o wide | grep fubar
Get the pods under those nodes (replace NODE_NAME_GOES_HERE with the name you got from the command above, e.g. ip-10-111-22-333.ec2.internal):
k get pod --field-selector=spec.nodeName=NODE_NAME_GOES_HERE -owide --all-namespaces
Little trick I learned from living in NYC.
There’s free street parking in neighborhoods like Ozone Park near JFK on streets that don’t have street cleaning, for example on 120th St between 133rd Ave and Sutter Ave. You can park there, and then take public transit or uber to JFK. I’ve done this at least twice now.
This is fairly low risk if you’re not going away for more than a week. The only issue is if you leave the car for too long I imagine it might be reported as abandoned and get towed.
You can do a similar sort of thing near LGA, which I’ve done MANY times now, but there are no streets without street cleaning, so you either need to make sure your trip is 6 days or less, or cough up the $65 ticket for street cleaning.
The nice thing about LGA, is that street parking is close enough to the airport that you can just walk to the terminal, or take a kick scooter and then lock it up at one of the bike racks outside the terminals.
I love not needing to spend $60-80 for airport transportation and being able to drive myself 95% of the way there. I usually walk to LGA too instead of taking an Uber after finding a spot.
Had to do this recently for a lot of test projects that were created in our Jira sandbox instance.
It’s a small python script using Jira API and the requests python library.
import requests
from requests.auth import HTTPBasicAuth
domain = "https://MY_JIRA_INSTANCE.atlassian.net"
admin_user = "JIRA_ADMIN@MY_COMPANY.com"
admin_token = "JIRA_ADMIN_TOKEN"
project_query = "PROJECTS_I_WANT_TO_DELETE"
def getJson(url, auth):
r = requests.request(
"GET",
url,
headers={"Accept": "application/json"},
auth=auth
)
return r.json()
def deleteProject(id, auth):
r = requests.request(
"DELETE",
domain + "/rest/api/3/project/" + id,
auth=auth
)
return r.text
search_url = domain + "/rest/api/3/project/search?query=" + project_query
auth = HTTPBasicAuth(admin_user, admin_token)
json = getJson(search_url, auth)
projectIds = []
# append results across all pages, while there's still a nextPage, to projectIds array
while "nextPage" in json:
nextUrl = json["nextPage"]
for searchResult in json['values']:
# optional safety check to make sure the right project is being added to the deletion array
# if "PROJECT_NAME_I_INTEND_TO_DELETE" in searchResult["name"]:
projectIds.append(searchResult['id'])
print("Number of project IDs found matching the search query: " + str(len(projectIds)))
json = getJson(nextUrl, auth)
# append a single page, or the last page of results, to projectIds array
for searchResult in json['values']:
# optional safety check to make sure the right project is being added to the deletion array
# if "PROJECT_NAME_I_INTEND_TO_DELETE" in searchResult["name"]:
projectIds.append(searchResult['id'])
print("Number of project IDs found matching the search query: " + str(len(projectIds)))
# delete projects in projectIds array
for index, id in enumerate(projectIds):
print("Deleting project " + id + ". Projects remaining: " + str(len(projectIds)-index))
print(deleteProject(id, auth))Here is yet another entry in my iOS developer journey in which I try to improve upon available official documentation.
Facebook’s login SDK for iOS has been around for a while and has gone through several iterations/updates. There are various tutorials online which have these issues among others:
So as with Parse, I will combine the steps for doing a quick and easy Facebook Login setup in Swift 3.
Quick Start
target 'XCODE-PROJECT-NAME' do use_frameworks! pod 'FacebookCore' pod 'FacebookLogin' pod 'FacebookShare' end
import FacebookCore
func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplicationLaunchOptionsKey: Any]?) -> Bool {
// Override point for customization after application launch.
SDKApplicationDelegate.shared.application(application, didFinishLaunchingWithOptions: launchOptions)
return true
}
func application(_ app: UIApplication, open url: URL, options: [UIApplicationOpenURLOptionsKey : Any] = [:]) -> Bool {
let handled = SDKApplicationDelegate.shared.application(app, open: url, options: options)
return handled
}
import FacebookLogin
class ViewController: UIViewController {
override func viewDidLoad() {
super.viewDidLoad()
// Do any additional setup after loading the view, typically from a nib.
let loginButton = LoginButton(readPermissions: [ .publicProfile ])
loginButton.center = view.center
view.addSubview(loginButton)
}
}
You should now have an access token with public profile permissions for the user account that signed in with the facebook login button.
Notes/Errors
So now that you set up a free Parse server on Heroku using my previous guide you might be wondering how to start using it in your iOS project. Checking the main Parse documentation shows a bunch of Objective-C, which isn’t helpful if you’re using Swift 3.
Here are the steps I gathered from perusing the web and some testing:
source 'https://github.com/CocoaPods/Specs.git' platform :ios, '10.0' use_frameworks! target 'PROJECT_NAME' do pod 'Parse' end
let configuration = ParseClientConfiguration {
$0.applicationId = "YOUR_PARSE_APP_ID"
$0.clientKey = "YOUR_PARSE_CLIENT_KEY"
$0.server = "https://PARSE_SERVER_NAME.herokuapp.com/parse"
}
Parse.initialize(with: configuration)
let testObj = PFObject(className: "testObj") testObj["foo"] = "bar" testObj.saveInBackground()
Notes/Troubleshooting
If XCode can’t find the Parse module with the import command after you open the new .xcworkspace file, try the following:
Parse Server is a great platform for managing logins and storing data used by your apps in the cloud.
You can install and use parse server on many different cloud hosting providers, but setting up Parse Server on Heroku is one of the few ways you can try out and use it for free.
Additionally you can also install Parse Dashboard on Heroku for managing and viewing data on your Parse Server using a nice GUI.
Sources:
At this point you can start using your Parse Server with its standard SDKs and REST interface.
If you had any issues with the automated deployment, you can also use the manual process in the Heroku devcenter source link above. The only thing you will need to do is make sure you set the Master_Key and App_ID by going to your Config Variables under your Heroku app’s Settings tab, and adding “MASTER_KEY” and “APP_ID” variables.
mkdir my-parse-dashboard cd my-parse-dashboard git init npm init npm install --save parse-dashboard
This will create a git repository for the parse-dashboard code and download the required code.
{
"apps": [
{
"serverURL": "https://parse-server38.herokuapp.com/parse",
"appId": "parseServer38",
"masterKey": "secretMasterKeySK$%@F09292",
"appName": "My Parse Server App"
}
],
"users": [
{
"user":"user1",
"pass":"securePass281"
}
]
}
web: ./node_modules/.bin/parse-dashboard --config ./parse-dashboard-config.json --allowInsecureHTTP
git add package.json Procfile parse-dashboard-config.json git commit -m "Initial Commit"
heroku login heroku create git push heroku master
heroku ps:scale web=1 heroku open
You should now be able to use a GUI to view and manage your Parse Server.
git add parse-dashboard-config.json git commit -m "updated blah blah" git push heroku master